Tim Stack

I changed the file-pattern property to look like the following and it seems to work fine: ``` "file-pattern": ".*\\.log", ``` Here's a screenshot:

Did you change the format file in "~/.lnav/formats/installed/custom_log.json"? If not, you'll need to rerun `lnav -i` to install the updated version.

What platform are you running it on (linux, macos)? How was it installed (snap, brew, …)? Can you try running it with `-d lnav-debug.log` and attaching that log file.

What connections are setup for your snap install, here's what I see on an Ubuntu 21.10 vagrant machine: ``` $ snap connections lnav Interface Plug Slot Notes home lnav:home :home...

It looks like the `msg` field ends with a line-feed, so that's where the extra line is coming from. I'll need to make some changes to allow the line to...

Since hidden fields are replaced with a single character, when the field is itself a single character, there's nothing to really hide. So, it just shows the original data.

I think "%i" should work for you, it shouldn't look for a fixed number of digits. However, it treats the value as milliseconds from the epoch and not pico seconds....

To clarify, there's a cluster of search hits and you're expecting 'n' to move to the next line instead of the next cluster? Do you think you can get used...

Not knowing there is a search hit because it's off-screen sounds like a problem in-and-of-itself. I'd like to try and address that before reverting the n/N change.

In the near future the keymap will be user-configurable, so you'll be able to define the keys to do whatever you like.