Yes, it works very well in my case, as the information, searched for, is either automatically part of the post process or is added routinely by the programmers later in the leading comments of the programs. Each CNC machined part at our location usually requires multiple setups or fixtures that are given a different operation number and each program a unique 1 to 5 digit program number.

The regex (regular expressions search patterns) can then extract the unique info for each program as each page is printed for a machine operator part programs binder compilation.

Thank You Mr. Grasin for the update that includes regex printout capabililities.
See attached images on how I use that feature to enhance the info printed in the headers or footers of each page.
The Program number regex searches for a pattern of digits preceded by small O, or large O, or a colon.
The Operation number regex searches for a pattern that is a "word" that starts with 'OP' and is followed by digits.

I currently thinking about using your so called identifiers used in the header or footer area of the printed page. (At least that's what the error message calls them, when I try to use one that the program doesn't know about.)
For example, the [FILENAME] identifier now returns the current filename.

Other new possible identifiers might be:
[WORD(7)] to return the seventh 'word' in file, etc.

[\[Oo:\]\[0-9\]{1,}] a Microsoft Word-like wildcard pattern in a identifier, in this case, using a backslash to be able to use square brackets in a pattern. This pattern would supposedly find and return the first word that starts with one of the three characters, capital o or small o or semicolon and is followed by a sequence of one or more numbers.

Also, possibly use identifiers as tags like they are being used in this forum message to format header and footer text. For example  [\color=red][FILENAME][\/color] to print the filename in red in the header.(Without the backslashes, of course.)

I like it.

Is there any way we can add an Identifier to printout the program number in the header. Unfortunately, we use another naming convention for our filenames that doesn't include the program number. That is usually the first word in the file for a Fanuc controller after the starting symbol '%'. like O7777 or :7777

Meanwhile, I temporarily add the number before printing and then delete it.

But it would be nicer with an automatic Identifier. (Maybe using regular expressions to find a pattern? Like in Microsoft Word they have wildcards like [Oo:][0-9]{1,} to find such a pattern)

The Colour CNC Syntax printout of the G-Code programming code looks great!

However, the lack of page numbering and date printed and filename in a header or footer of the printer page of your software's printout is forcing us to go to another program like Microsoft Word to get the required info onto the printed page for our documentation.

Would you add those print layout features to your software for colour printing or add the ability to save the colour formatted file as a .docx Word 2007 file format?