Hi,

During work on https://github.com/rust-lang-nursery/log/ documentation, we wanted to add link to this crate as one of the most popular implementations. Unfortunately it has no documentation. Currently it does not seam to be intended for 3'rd party adoption. Would you be open to adding few sentences to docs?

Please refer to: rust-lang/log@dbd3c44#r119920413

Currently, env-logger has been updated to 0.9.0, maybe it's time to release a new version. :)

Given the following code where logme just calls log::warn!("warning")`

gives the following output, despite format_module_path(false) since 0.5.0

Compared to 0.4.0 (which behaves as I would expect):

This line should be added to src/lib.rs:

pub use env_logger;

so crates using pretty-env-logger do not have to add env_logger to their own dependencies (if they want to customize logging with pretty_env_logger::formatted_builder).

I don't see this in the example.

The github metadata (the text at the top of the repo, above the readme, above the file list on the repo homepage) links to https://crates.io/pretty_env_logger, which is not a valid link; it should be https://crates.io/crates/pretty_env_logger.

Also there is no tag in repository...

It would be nice to have more options for configuring an env_logger Builder when using pretty_env_logger::formatted_builder() such as parse_env() or parse_default_env() to make it easier to be able to configure a logger with defaults in case RUST_LOG hasn't been set.

Executing this code

use log::{trace, debug, info, warn, error};

fn main() {
    pretty_env_logger::formatted_builder().init();

    trace!("a trace example");
    debug!("deboogging");
    info!("such information");
    warn!("o_O");
    error!("boom");
}

with

RUST_LOG=trace cargo run

prints

 ERROR terminal_image > boom

and this is quite confusing, because I expected it to print all log levels (it ignores the environment variable).

the env_logger package provides env_logger::builder().is_test(true).try_init() which allows logs to be captured. It would be nice to expose this in this crate as well.

See https://docs.rs/crate/pretty_env_logger/0.2.2

I'm using pretty-env-logger (through quicli) for a long-lived daemon, and I would need to dynamically change its log level at runtime (my daemon sends logs via network, and something "in the cloud" may ask it to log more or less).
How is it possible to do that ? Or if not possible currently, would it be possible as a feature ?

When I put the example in main.rs. Ran with RUST_LOG=main=trace cargo run. Nothing was print out. It is an issue with pretty_env_logger or cargo itself? Because running RUST_LOG=trace cargo run will print out everything, which is not what we want.

Is there a straighforward way to add redaction/filtering?

@seanmonstar I just created a fork of your logger to expose the env_logger::Builder - I like the formatting but was needing more control over the logger... I also added some more examples.

If you are interested in merging the changes I can send you a pull request for review.

I tried using formatted_builder() and now the RUST_LOG env var seems to be completely ignored. Is this function working?

I also saw these comments implying that the function is broken: #41 (comment) #20 (comment)

So that I have proof that this is, in fact, pretty.

Thanks for this crate!

You are currently using env_logger with default features. This includes the regex crate with default features which adds about 1.3MB to a binaries size (see rust-lang/regex#613).

Could you maybe add (and proxy) the features of env_logger so that a consumer of your crate can disable the default features (ie "regex")?

Something along the lines of the following would help:

[features]
default = ["termcolor", "atty", "humantime", "regex"]
termcolor = ["env_logger/termcolor"]
atty = ["env_logger/atty"]
humantime = ["env_logger/humantime"]
regex = ["env_logger/regex"]

It appears that there are a bunch of staled issues and PRs, if it's not maintained anymore, the repository should be archived or transferred to someone, avoiding unnecessary creation of PRs and issues.

We (Fedora Rust SIG) would appreciate if you would not use deny warnings in code, but rather use it from CI (-D warnings).

BUILDSTDERR:      Running `/usr/bin/rustc --crate-name pretty_env_logger src/lib.rs --color never --crate-type lib --emit=dep-info,link -C opt-level=3 -C metadata=13a6cbd344d92b81 -C extra-filename=-13a6cbd344d92b81 --out-dir /builddir/build/BUILD/pretty_env_logger-0.3.0/target/release/deps -L dependency=/builddir/build/BUILD/pretty_env_logger-0.3.0/target/release/deps --extern chrono=/builddir/build/BUILD/pretty_env_logger-0.3.0/target/release/deps/libchrono-842eeac55f65145c.rlib --extern env_logger=/builddir/build/BUILD/pretty_env_logger-0.3.0/target/release/deps/libenv_logger-aafab70dab9d3a16.rlib --extern log=/builddir/build/BUILD/pretty_env_logger-0.3.0/target/release/deps/liblog-afd98fddddc8f6a6.rlib -Copt-level=3 -Cdebuginfo=2 -Clink-arg=-Wl,-z,relro,-z,now`
BUILDSTDERR: error: use of deprecated item 'env_logger::Builder::parse': use `parse_filters` instead.
BUILDSTDERR:    --> src/lib.rs:126:17
BUILDSTDERR:     |
BUILDSTDERR: 126 |         builder.parse(&s);
BUILDSTDERR:     |                 ^^^^^
BUILDSTDERR:     |
BUILDSTDERR: note: lint level defined here
BUILDSTDERR:    --> src/lib.rs:1:9
BUILDSTDERR:     |
BUILDSTDERR: 1   | #![deny(warnings)]
BUILDSTDERR:     |         ^^^^^^^^
BUILDSTDERR:     = note: #[deny(deprecated)] implied by #[deny(warnings)]
BUILDSTDERR: error: use of deprecated item 'env_logger::Builder::parse': use `parse_filters` instead.
BUILDSTDERR:    --> src/lib.rs:145:17
BUILDSTDERR:     |
BUILDSTDERR: 145 |         builder.parse(&s);
BUILDSTDERR:     |                 ^^^^^
BUILDSTDERR: error: aborting due to 2 previous errors
BUILDSTDERR: error: Could not compile `pretty_env_logger`.

It looks like env-logger was updated, and that's it?

https://github.com/seanmonstar/pretty-env-logger/compare/v0.4.0..v0.5.0

Is it possible to disable the automatic alignment of log messages? This often causes huge space as soon as there is one significantly longer target, so I would rather completely disable it and print > message here directly after the target with only a single space in between.

#5 is still open, but I don't know whether it refers to this or something different.

In env_logger it's possible to provide a default log level by using:

env_logger::from_env(Env::default().default_filter_or("info")).init();

Would you consider adding this feature (or maybe accepting a PR)?