You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When triggering a "plugin" alert, there is a possibility to add Parameters for the alert command parameters.
One of the parameters is "%L = Line number for keyword hit".
Bug
This parameter always returns line number 1 less than triggered line.
For example, alert triggered at line 534, the %L parameter returns 533. It is almost like it confuses the header of the file somehow. Same problem if I set the CSV-columnizer with or without "header"
LogExpert Version: 1.9.0
Windows Version 10
Used Columnizer : CSV
Is this version specific or a new problem: No
thanks, Best app in its category!
The text was updated successfully, but these errors were encountered:
The problem is, that the CSV Columnizer currently does not support this feature, because it does not implement the ILogLineColumnizerCallBack that is needed for the ProcessLauncher-Plugin!
Hi, I simply open a cmd.exe window with some coloring, by passing this parameter (which gives wrong line number):
cmd.exe /t:47 /K Title LogExpert - "%T" && Echo %date%-%time% FATAL ERROR at line "%L" && echo Message:: "%C"
When triggering a "plugin" alert, there is a possibility to add Parameters for the alert command parameters.
One of the parameters is "%L = Line number for keyword hit".
Bug
This parameter always returns line number 1 less than triggered line.
For example, alert triggered at line 534, the %L parameter returns 533. It is almost like it confuses the header of the file somehow. Same problem if I set the CSV-columnizer with or without "header"
thanks, Best app in its category!
The text was updated successfully, but these errors were encountered: