Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

change(mac): remove 'Use verbose Console logging' option #11525

Closed
1 of 8 tasks
sgschantz opened this issue May 24, 2024 · 0 comments · Fixed by #12431
Closed
1 of 8 tasks

change(mac): remove 'Use verbose Console logging' option #11525

sgschantz opened this issue May 24, 2024 · 0 comments · Fixed by #12431
Assignees
Milestone

Comments

@sgschantz
Copy link
Contributor

sgschantz commented May 24, 2024

In the Options tab of the Configuration window, there is currently a checkbox labeled 'Use verbose Console logging' as shown below. As of PR #11515, it is now obsolete and should be removed.

image

When enabled, this option caused many additional statements to be written to the log. However, these log statements would not be treated differently than other statements written to the log. Unified Logging in macOS provides a means of setting the log levels that is more efficient and cleaner to code.

Instead of checking for the option and writing a basic log statement, as of #11515, we now use the API os_log_debug. The user will see these statements if they are streaming to the Console while running Keyman and have enabled the option Action -> Include Debug Messages. They can also filter based on the subsystem and category to focus on a subset of the statements.

More info on macOS Logging:

The unified logging system provides a comprehensive and performant API to capture telemetry across all levels of the system. This system centralizes the storage of log data in memory and on disk, rather than writing that data to a text-based log file. You view log messages using the Console app, log command-line tool, or Xcode debug console. You can also access log messages programmatically using the OSLog framework.

Also, info on os_log_debug:

Debug-level messages are only captured in memory when debug logging is enabled through a configuration change. They’re purged in accordance with the configuration’s persistence setting.

Keyman apps

  • Keyman for Android
  • Keyman for iPhone and iPad
  • Keyman for Linux
  • Keyman for macOS
  • Keyman for Windows
  • Keyman Developer
  • KeymanWeb
  • Other - give details at bottom of form
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants