I'd just like to thank you for writing this. It's perfect.
On Monday, May 28, 2012 12:17:30 PM UTC+1, Peter Taoussanis wrote:
Hi everyone,
I recently lost it after spending 5+ hours trying to figure out why Log4j
had suddenly started swallowing all my messages [again]. Anyway, decided
On Fri, Mar 15, 2013 at 7:34 PM, adam.neil...@healthunlocked.com wrote:
I'd just like to thank you for writing this. It's perfect.
I'll second that! I've been using Timbre lately and it has been really
useful.
--
--
You received this message because you are subscribed to the Google
Groups
You're both very welcome, thanks for letting me know you've been enjoying
the lib!
BTW For those coming across this post only now, please note that the
Clojars URL has changed: https://clojars.org/com.taoensso/timbre. Anyway,
the newest version is always listed on GitHub:
Hi everyone,
I recently lost it after spending 5+ hours trying to figure out why Log4j
had suddenly started swallowing all my messages [again]. Anyway, decided
it'd be infinitely saner to write something simple for my own purposes. I'm
posting it here in case someone else might find it useful.
Looks good! As you said, logging is just too damn complicated in java.
Suggestion: change timbre/config to a function, seems way nicer to call
(timbre/config :current-level :warn)
rather than
(swap! timbre/config assoc :current-level :warn)
Jonathan
On Mon, May 28, 2012 at 1:17 PM, Peter
Done!
Having said that, I don't suggest anyone really edit their config
line-by-line like this. What I do is create a map of everything I need
during environment config and just merge it over the Timbre defaults with
something like this:
(defn deep-merge-with ; From clojure.contrib.map-utils
Thank you!! I'm glad to know that it's not only me who thought Log4j
was a terrible solution for logging in Clojure :)
On Mon, May 28, 2012 at 7:17 PM, Peter Taoussanis ptaoussa...@gmail.com wrote:
Hi everyone,
I recently lost it after spending 5+ hours trying to figure out why Log4j
had
