Up to [cvs.NetBSD.org] / pkgsrc / devel / ruby-console
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
devel/ruby-console: update to 1.35.1 1.35.0 (2026-05-19) * Align decimals in elapsed time display. (#84) * Fix handling of Errno::ENODEV errors when calculating the width of a terminal that was been re-opened to File::NULL 1.35.1 (2026-05-19) * Add missing context files to gemspec. * Fix gem metadata.
devel/ruby-console: update to 1.30.2 1.30.0 (2025-03-07) Introduce Console::Config for fine grained configuration. Introduced a new explicit configuration interface via config/console.rb to enhance logging setup in complex applications. This update gives the application code an opportunity to load files if required and control aspects such as log level, output, and more. Users can override default behaviors (e.g., make_output, make_logger, and log_level) for improved customization. # config/console.rb def log_level(env = ENV) # Set a custom log level, e.g., force debug mode: :debug end def make_logger(output = $stderr, env = ENV, **options) # Custom logger configuration with verbose output: options[:verbose] = true Logger.new(output, **options) end This approach provides a standard way to hook into the log setup process, allowing tailored adjustments for reliable and customizable logging behavior. 1.30.1 (2025-03-09) * Remove circular require 1.30.2 (2025-03-10) * Add missing require.
devel/ruby-console: update to 1.29.0 1.28.0 (2024-11-05) * Add support for Kernel#warn redirection to Console.warn. 1.28.1 (2024-11-05) (Unknown) 1.29.0 (2024-11-06) * Don't make Kernel#warn redirection to Console.warn the default behavior, you must require 'console/warn' to enable it. * Remove deprecated Console::Logger#failure. Consistent Handling of Exceptions Console.call and all wrapper methods will now consistently handle exceptions that are the last positional argument or keyword argument. This means that the following code will work as expected: begin rescue => error # Last positional argument: Console.warn(self, "There may be an issue", error) # Keyword argument (preferable): Console.error(self, "There is an issue", exception: error) end
devel/ruby-console: update to 1.25.2 1.23.7 (2024-04-20) * The exception backtrace should be split into at most 3 pieces. 1.24.0 (2024-04-22) * Add compatible shim for Exception#detailed_message. (#58) * Better output formatting of options. 1.25.0 (2024-05-03) * Separation of output formatting from log generation/schema. (#60) * Use Console::CapturedOutput everywhere. * Improve getting started guide. * Remove test file. * Add guidelines for custom events. * Set minimum version of fiber-local gem. * Compatibility with previous event argument. 1.25.1 (2024-05-03) * Add tests for Console::Event::Spawn. 1.25.2 (2024-05-04) * Apply subject/level filtering in Filter#call.
devel/ruby-console: update to 1.23.1 1.21.0 (2023-08-07) * Expose direct interface on Console. (#46) * Default to the current console. (#47) 1.22.0 (2023-08-11) What's Changed * Introduce new "Safe" JSON serialization implementation. (#48) 1.23.0 (2023-08-11) * Remove the Encoder that is no longer used. (#49) * Introduce Console::Format for format handling. (#50) 1.23.1 (2023-08-11) * Capture enough information to debug SystemStackErrors when dumping logs. (#51)
devel/ruby-console: update to 1.20.0 1.19.0 (2023-08-03) * Add adapter module for external gems. 1.20.0 (2023-08-02) What's Changed * Modernize gem. by @ioquatix in #45 * Encode serialized output to avoid encoding errors. by @ioquatix in #44 * This release drops support for Ruby 2.7.
ruby-console: add missing file
devel/ruby-console: add package version 1.16.2 Required by ruby-async package. Console Provides beautiful console logging for Ruby applications. Implements fast, buffered log output. Motivation When Ruby decided to reverse the order of exception backtraces, I finally gave up using the built in logging and decided restore sanity to the output of my programs once and for all! Features * Thread safe global logger with per-fiber context. * Carry along context with nested loggers. * Enable/disable log levels per-class. * Detailed logging of exceptions. * Beautiful logging to the terminal or structured logging using JSON.