#logging #tui #log #filelog #cli


Replacement for the simplelog crate, which is simpler and has clearer dependencies

4 releases

0.1.3 Oct 22, 2023
0.1.2 Oct 22, 2023
0.1.1 Oct 17, 2023
0.1.0 Oct 14, 2023

#371 in Command-line interface

Download history 3671/week @ 2024-03-14 3122/week @ 2024-03-21 2891/week @ 2024-03-28 3294/week @ 2024-04-04 3198/week @ 2024-04-11 3403/week @ 2024-04-18 3712/week @ 2024-04-25 4797/week @ 2024-05-02 3051/week @ 2024-05-09 3110/week @ 2024-05-16 3156/week @ 2024-05-23 3288/week @ 2024-05-30 2817/week @ 2024-06-06 3183/week @ 2024-06-13 3712/week @ 2024-06-20 3490/week @ 2024-06-27

13,628 downloads per month
Used in 11 crates (via r3bl_rs_utils_core)



This is a fork & rewrite of the https://github.com/drakulix/simplelog.rs repo, for use by the https://crates.io/crates/r3bl_rs_utils_core crate.


How to log things, and simply use the logging facilities

The simplest way to use this crate is to look at the r3bl_rs_utils_core::try_to_set_log_level function in the r3bl_rs_utils_core crate as the main entry point. By default, logging is disabled even if you call all the functions in the file_logger module in that crate: log_debug, log_info, log_trace, etc.

How to change how logging is implemented under the hood

Under the hood the simplelog crate is forked and modified for use here. The following are details for people who want to work on changing the underlying behavior of the logging engine itself, and not for folks who just want to use this crate.

r3bl_simple_logger provides a series of logging facilities, that can be easily combined.

  • SimpleLogger (very basic logger that logs to stdout)
  • TermLogger (advanced terminal logger, that splits to stdout/err and has color support) (can be excluded on unsupported platforms)
  • WriteLogger (logs to a given struct implementing Write, e.g. a file)
  • CombinedLogger (can be used to form combinations of the above loggers)
  • TestLogger (specialized logger for tests. Uses print!() / println!() for tests to be able to capture the output)

Only one Logger should be initialized of the start of your program through the Logger::init(...) method. For the actual calling syntax take a look at the documentation of the specific implementation(s) you wanna use.