I remember that too - Quick question though, have you tried using copilot to try and make one?

I made a quick-and-dirty one for Notepad++ many years ago, although it was not much more than line-based highlighting based on the severity of each message.

I can’t find the definition file anymore, but I remember it was fairly easy to do: https://npp-user-manual.org/docs/user-defined-language-system/

ok well 45 mins of playing around with copilot I was able to put this together……

To install the extension you should just need to run 

code --install-extension path/to/extension.vsix

or drag drop into the list of installed extensions. 
To get the typical blue/red highlighting you also need to add this to your settings.json file
 

"editor.tokenColorCustomizations": {
  "textMateRules": [
    {
      "scope": "markup.inserted.fme-log.warnline",
      "settings": { "foreground": "#0070f3", "fontStyle": "bold" }
    },
    {
      "scope": "markup.deleted.fme-log.errorline",
      "settings": { "foreground": "#e53935", "fontStyle": "bold" }
    }
  ]
}

 After that all my FME Log files now look like this
 

on the left you can see the extension added. I wouldn’t trust what the AI wrote in the description but it does at least uninstall properly.  

 

This is a great  ​@virtualcitymatt ! Awesome thanks a lot!

well don’t thank me - this was 100% vibe coded for free haha

ok so I’ve updated it….

It should now highlight sql form the SQL Executer as well as filepaths. You should also now be able to right click on a path and either copy it or open it up in windows explorer.

I’ve also added a feature which is supposed to highlight lines in the log where the time has changed by more than 2 seconds. 

It’s not really well tested at all and I have no idea how well it will perform on really bit log files. 

But I think I’ll be using it. Thanks for the neat idea.

Oh and you need to update the settings.json again to include the following:
 

"editor.tokenColorCustomizations": {
  "textMateRules": [
    {
      "scope": "markup.inserted.fme-log.warnline",
      "settings": { "foreground": "#0070f3", "fontStyle": "bold" }
    },
    {
      "scope": "markup.deleted.fme-log.errorline",
      "settings": { "foreground": "#e53935", "fontStyle": "bold" }
    },
    {
      "scope": "source.sql.embedded.fme-log",
      "settings": { "foreground": "#b58900", "fontStyle": "italic" }
    },
    {
      "scope": "keyword.other.sql",
      "settings": { "foreground": "#268bd2", "fontStyle": "bold" }
    },
    {
      "scope": "constant.other.fme-log.filepath.windows",
      "settings": {
        "foreground": "#FFB74D",
        "fontStyle": "italic"
      }
    },
    {
      "scope": "constant.other.fme-log.filepath.linux",
      "settings": {
        "foreground": "#FFB74D",
        "fontStyle": "italic"
      }
    },
    {
      "scope": "constant.other.fme-log.filepath.url",
      "settings": {
        "foreground": "#FFB74D",
        "fontStyle": "italic"
      }
    }
  ]
}

Nothing wrong with a bit of vibe coding! Looks great ​@virtualcitymatt

If you’re taking improvement requests, collapsible sections for Logger messages
 

Nothing wrong with a bit of vibe coding! Looks great ​@virtualcitymatt

If you’re taking improvement requests, collapsible sections for Logger messages
 

 

Nice idea - the AI has now added some collapsible sections.

I’ve also added a command which will extract lines by status.

use CTRL+Shift+P and look for FME Log: Filter Log By Status

Nothing wrong with a bit of vibe coding! Looks great ​@virtualcitymatt

If you’re taking improvement requests, collapsible sections for Logger messages
 

 

Nice idea - the AI has now added some collapsible sections.

I’ve also added a command which will extract lines by status.

use CTRL+Shift+P and look for FME Log: Filter Log By Status

That is so SWEET!

Nothing wrong with a bit of vibe coding! Looks great ​@virtualcitymatt

If you’re taking improvement requests, collapsible sections for Logger messages
 

 

Nice idea - the AI has now added some collapsible sections.

I’ve also added a command which will extract lines by status.

use CTRL+Shift+P and look for FME Log: Filter Log By Status

Great stuff!

Could you open source it - stick it on github?