Erwin Bonsma

Enable debug log via --debug option

Create plain 2D variant of logo

Minor update to logo

Note that GrandPerspective scanned many more folders on the local directory, and printed zero error messages about "No such file or directory". What do the paths look like in the error messages? Do they look correct? Are they accessible from the terminal, for example using ls -al <path>? I suspect the issue you are experiencing is specific to the Samba server software that is used. GrandPerspective's scanning logic uses the generic FTS API. There's one thing that may still be worth a try (but that...

Also, it seems there is a second issue: you expect that Scanning <path> messages will have path information when GrandPerspective has --args -logAll YES, but I observe the messages have the path information censored.</path> That is strange. The "Scanning <path>" messages are logged with a public modifier to a trusted logger that is disabled by default. That should prevent sensoring, and does so on my system. Maybe this is a limitation of your version of macOS (14.8), which is fairly old.</path> Anyway,...

Incorrect `log` command arg in "How to enable and view diagnostic logs" help page

Thanks for the report. It looks as if this is a change in the log command, as I think you are on an older version of macOS than I am (I am on Golden Gate 27.0 Beta, whereas I think you are on Sonama 14.8, from the info you shared on another bug report). I am assuming it used to be --debug, and now is --level-debug. This is the help that I get: options: -l, --level default | info | debug Include events at, and below, the given level Anyway, --debug is still also supported. The semantics are slightly...

Bug tickets does not include 3.8.0 as Milestone value