I use NotePad++ which will generate a list of all the hits which is what Miyako’s parsing script does. Miyako’s script is much easier.
Tom > On Sep 19, 2019, at 14:03, Chip Scheide <[email protected]> wrote: > > it is not that I can not search - it is that I did not know what to > search for :) > > BTW - > in most browsers Command/Control + F will open a search entry area > which will allow you to search the contents of the current web page (or > in this case log file). > > Chip > > On Thu, 19 Sep 2019 13:49:30 -0700, Tom Benedict wrote: >> Browsing the log file manually is tedious, so I use a text editor to >> look for “warning” or “error”. That’s always been enough for me >> to find any outstanding “Anomalies”. If you’ve already done that >> there must be something else which is considered an anomaly. >> >> Sorry this isn’t very useful. >> >> Tom Benedict >> >>> On Sep 19, 2019, at 13:42, Chip Scheide via 4D_Tech >>> <[email protected]> wrote: >>> >>> I moved a large system to v16, ran MSC. >>> Verify - anomalies found - 2 PICTs --removed >>> Repair - anomalies found - orphaned method --removed >>> Verify - anomalies found - I can not find it >>> >>> there is no 'warning' in the log file. >>> what should I be looking for? >>> is there a parser available? >>> >>> note: why doesn't the log file total lines of code? >>> >>> Thanks >>> Chip >>> >> >> > --------------- > Gas is for washing parts > Alcohol is for drinkin' > Nitromethane is for racing ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
