Tim Stack

@cattz The '-d' should still work, it hasn't been removed. Can you give some sample log files, I can try to help in defining the format.

> if the format changes mid-file and the user only cares about the newest format. The latest version (v0.8.5), now supports multiple regex patterns per file. In other words, if...

> I would also like the ability to force a specific log that I'm looking at to be "generic" somehow; is there any way to do that? Can't figure it...

@macintacos Thanks for getting back > I'm looking at a log file with a certain parser applied (lets say it's a user defined one) and I'd like to switch to...

> My logs are mostly json and I have a working config for those but some of the lines are non-json and mostly appear towards the top of my log...

> I'd also like to request the ability to change/override the format of a particular log file manually. [...] > I'd like to just quickly override the auto detection with...

> Since the log format is detected at startup (I think?), you have to restart once there are matching lines etc which could be a few minutes into your workflow,...

> I suppose one improvement would be to print out a link to something like regex101.com to help streamline the debugging process. I have pushed an integration with regex101.com to...

The `lnav -i` is just for installing format files and log files should not be passed in. Just run ``` lnav -i myformat-json ``` And then run: ``` lnav my-logs.log...

The `file-pattern` is a regular expression that needs to match the log file name. Try changing it to something like `.*\.log` so that it will match file names ending with...