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
As I got an answer of another issue of mine, I gave the plugin another try.
But somehow it does not really work as expected.
As a test I created a simple log file that adheres to the built-in "Pipe-separated" log format and as I do not get the "Log format not recognized" header I assume the log format per-se is recognized.
If I replace all pipes, I get the header, so I'm also pretty sure the plugin is doing "something".
The log file I created consist of these lines:
The error stripe is about the only thing that seems to work properly:
This is what I see:
So for example the lines are not painted in red, yellow, and green.
The "Hide lines ..." and "Show only lines ..." intentions also seem to work as intended.
But if I for example do "Toggle Time Highlighting" as @smirok showed in #159 I do not get different colors, but all in red and additionally the previous linebreak highlighted:
If I do "Highlight 'message2'" while having the caret on "message2", all lines containing that message are highlighted, but also including the previous linebreak:
If I do "Highlight this column" on a log level, all lines get the same highlighting except for the error line, and also the previous linebreak highlighted:
While testing further, it might just be an unlucky choice of colors that are very similar, because if I do it on the level, colors alternate but also are quite similar:
Doing "Highlight this column" on the last column does not work at all, like also all other column specific options like "Hide lines with ... in this field" and others, those options all are missing from the intention popup.
Doing "Jump to Source", jumps to a very strange log line that is not even similar to those dummy log messages.
Time highlight does also highlight the previous field separator or message start match (custom log format here):
If the log file is read-only due to the "Allow editing log files smaller than" setting, also all intention actions are not available. If I press Alt+Enter nothing happens, if I right-click and say "Show Context Actions" I only get a "No context actions available at this location" message.
So after writing all this, I think the main points are:
lines are not colored according to log level
Highlighting highlights the previous linebreak
Automatic highlight colors are often too similar
Time Highlighting does not show the advertised time distance
The last field does not have the field intentions
Jump to Source behaves strange
Time Highlighting as it does right now does not only highlight the time, but also highlights the preceding field separator
If the log file is read-only due to the "Allow editing log files smaller than" setting, also all intention actions are not available
The text was updated successfully, but these errors were encountered:
Ah, I at least got the line text highlighting to work now, by changing the "Capture Group" from 1 to 0 in all three "Patterns".
But I also added "Show on stripe" to the warning pattern which now highlights the line, but on the error stripe it is still not shown. :-/
Could you please let me know which IDE you use and which version of Ideolog you have?
I'm trying to reproduce it on the latest version of Ideolog:
I use the same log file as you shared
The default highlighting patterns fits perfectly for the log file
The error stripe is actually get broken
The issue with incorrect background highlighting after the newline is a known issue, I'll investigate it further.
The reason why you have only red "time highlighting" is the big difference between events (1 minute). Please find the example below with smaller distances between adjacent log events:
"Highlight this column" looks broken, I'll investigate it.
Agree with you on color choices, I'll fix it.
Highlighting on the last column is probably broken as well.
"Jump to Source" is a bit of a magic, it could works only for log formats that contain "category" capture group (like IntelliJ IDEA logs or your log format), but probably even for them it doesn't work correctly.
Time highlight does also highlight the previous field separator or message start match (custom log format here) - I'll discover it.
As I got an answer of another issue of mine, I gave the plugin another try.
But somehow it does not really work as expected.
As a test I created a simple log file that adheres to the built-in "Pipe-separated" log format and as I do not get the "Log format not recognized" header I assume the log format per-se is recognized.
If I replace all pipes, I get the header, so I'm also pretty sure the plugin is doing "something".
The log file I created consist of these lines:
The error stripe is about the only thing that seems to work properly:
This is what I see:
So for example the lines are not painted in red, yellow, and green.
The "Hide lines ..." and "Show only lines ..." intentions also seem to work as intended.
But if I for example do "Toggle Time Highlighting" as @smirok showed in #159 I do not get different colors, but all in red and additionally the previous linebreak highlighted:
If I do "Highlight 'message2'" while having the caret on "message2", all lines containing that message are highlighted, but also including the previous linebreak:
If I do "Highlight this column" on a log level, all lines get the same highlighting except for the error line, and also the previous linebreak highlighted:
While testing further, it might just be an unlucky choice of colors that are very similar, because if I do it on the level, colors alternate but also are quite similar:
Doing "Highlight this column" on the last column does not work at all, like also all other column specific options like "Hide lines with ... in this field" and others, those options all are missing from the intention popup.
Doing "Jump to Source", jumps to a very strange log line that is not even similar to those dummy log messages.
Time highlight does also highlight the previous field separator or message start match (custom log format here):
If the log file is read-only due to the "Allow editing log files smaller than" setting, also all intention actions are not available. If I press Alt+Enter nothing happens, if I right-click and say "Show Context Actions" I only get a "No context actions available at this location" message.
So after writing all this, I think the main points are:
The text was updated successfully, but these errors were encountered: