Logview Versions Save

This release improves mode initialization and timestamp handling in case library datetime fails to determine the system timezone and nothing has been set explicitly in variable datetime-timezone. As far as I know, this can affect only Windows machines and only in some timezones.

This release repairs a non-working narrowing-locking workaround rewrite in 0.17.2. There are no other changes.

Another bugfix release:

• Logview should now also accept filenames like example.log.2024-04-15-22-77 (previously such files were ignored because of the hyphens).
• Fixed a couple of minor problems with displaying timestamp differences.
• Upgraded narrowed-locking workaround to work on upstream Emacs (would-be-30).

This release fixes an old (judging from source history) bug with views not being saved after some editing operations. This could result in view definitions being lost.

New in this release:

• Results of filters in buffer popped up by f or Y are now previewed on-the-fly as you edit them. However, if you dislike this, you can simply customize variable logview-preview-filter-changes. The variable can also be toggled per-buffer using o p or from the filter buffer using C-c C-p.
• New command C-c C-a in the filter buffer applies edited filters, but doesn't close it, allowing you to continue editing. In other words, it works like C-c C-c, only without closing the buffer. This is particularly useful if you disable filter previewing mentioned in the previous item.
• Submode formats (variable logview-additional-submodes) can now force regular expressions for parts NAME, THREAD and IGNORED, if the defaults generated by Logview are not suitable. The syntax for this is a bit verbose: <<RX:PART:REGEX>>, e.g. <<RX:IGNORED:[a-z]+>>, but this is not supposed to be a frequently needed feature.

0.16.4 bumps datetime dependency to recently released 0.8 and tries to work around some timestamp format changes in Java 17. Unfortunately, not everything can be done automatically here, so some previously autoguessable formats will become unrecognized. On the other hand, without the upgrade we'd never autoguess certain timestamps generated by Java 17, so it's a situation where one cannot have everything.

However, if your logs use typical timestamps like yyyy-MM-dd HH:mm:ss.SSS, you won't be affected at all.

Restore compatibility with upcoming Emacs 29 yet again. Apparently, they have decided that renaming just once was not enough.

This release fixes a bug where Logview wouldn't detect entries with messages that contained no text in the first line at all, e.g. if you used sth. like log.info ("\n..."); in your program.

This release restores compatibility with upcoming Emacs 29 that was again broken by renames in Emacs source code.

This release drastically improves responsiveness of Emacs when you filter out almost everything in a huge log buffer.

Previously (since release 0.10), Logview would become busy fontifying and filtering the log until it could at least fill the first screen with visible entries. With tens-of-megabytes log files this could mean a full freeze of Emacs for up to several minutes, which was not user-friendly at all.

Now Logview will periodically make short pauses, showing not-yet-processed entries in a dimmed color. Additionally, you can continue navigating the log or even switch to another buffer and edit it, even if Emacs will be somewhat laggy. It is even possible to change the filters (e.g. just remove them all using R or pop a buffer for editing with f) if you feel that even when filtering is done for the whole buffer, it won't produce any useful results — e.g. if you have made a typo.