Laravel log level parsing may not work with filenames of more than 1 word

[serious-angel]

lnav version

v0.14.1

---

Describe the bug

Wonderful day!

Thank you for the marvel, art you do!

Is it possible that lnav does not properly support Monolog log level parsing if the log file has more than one word like currency-exchange or user-settings?

I've attached a preview of how it looks to the message.

Best and kind regards

---

To Reproduce

Write into a Laravel 10+ Monolog logger file with format, for example:

• :/storage/logs/$hostname/payments/payment-systems-2026-07-16.log
• :/storage/logs/$hostname/user/user-settings-2026-07-16.log

---

[serious-angel]

@coyaSONG , thank you very much for the change!

I am sorry to tell, but it seems like there's a possible issue with the formatter configuration change tested.

It seems like whenever debug exists in the name of the log, its color does not respect the actual level:

[tstack]

It seems like whenever debug exists in the name of the log, its color does not respect the actual level:

Hmm, I'm not able to reproduce that...

Perhaps there is something else that is not matching on those lines? Would you be able to share the full log lines so I can test?

[serious-angel]

Hmm, I'm not able to reproduce that...

@tstack , perhaps our configuration is different? I see the generic_log above:

How did you configure the Lnav? I've created the file you created in:

$ ls -las ~/.lnav/formats/installed/laravel_log.json 
4 -rw-rw-r-- 1 user user 1305 Jul 16 17:04 /home/user/.lnav/formats/installed/laravel_log.json