Rolf Kristensen

Do not think that will be trivial to draw icons unless there is some magic inside [Microsoft ListView](https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.listview)

You can setup an external tool, that truncates the file the way you like, and setup a keyboard-shortcut to execute the external tool inside SnakeTail.

Think there would be an overhead if having to scan for keywords, when opening an existing file. There is already logic for updating `Hits=`-counter in View-Title. Controlled by `keywordMatch.LogHitCounter`

Pull-requests are most wellcome for improving the WIX-installer-project: https://github.com/snakefoot/snaketail-net/blob/master/SnakeTail.Wix/Product.wxs

Not sure how to answer this question. But maybe it is more venting of frustrations. You are completely right that it will be a breaking change to adjust `int` to...

The logic for generating the NLog.Schema XSD that includes `default`-value in output, just calls the default-constructor for the target, and then probes the target-properties for their initial-value (default value).

| Before - Method | Mean | Error | StdDev | Gen0 | Allocated | |---------------------------- |--------------:|-----------:|-----------:|-------:|----------:| | CreateOneProperty | 43.52 ns | 0.152 ns | 0.135 ns | 0.0433...

I like the approach with parsing `string basePropertyName` and using recursion. Would it be possible that `DottedRecursion` becomes an option-parameter on the NLog JsonSerializeOptions (similar to `MaxRecursionLimit`), and then move...

Think with the latest change to handle IEnumerable, then the pull-request looks ready to me. Do you have any more planned changes?

Really appreciates the work you have done, and also overcoming my bad advice about trying to move the logic into the NLog JsonConverter. Like that the code is short and...