On Apr 12, 2:46 pm, ataggart wrote:
> Providing a mechanism which is simple, and does what one expects (an
> open question) consistently across different backing implementations
> is not as easy as it may seem.
Ideally, we can just cover the common base case, and expose machinery
for the user t
On Apr 10, 7:48 pm, Paul Legato wrote:
> Hi,
>
> I'd like to suggest two enhancements to clojure-contrib.logging:
>
> 1) There should be an easy way to set the current log level threshold
> (DEBUG, WARN, etc.)
I'd like that too. Alas, the complexity of hierarchical logging
libraries, coupled w
Just a reminder that logging has moved to it's own repository in the
clojure space. It can be found at
http://github.com/clojure/tools.logging
and is where all future development of the library should exist. If you
would like to submit patches for logging, please do so against the new
proje
Hi,
I'd like to suggest two enhancements to clojure-contrib.logging:
1) There should be an easy way to set the current log level threshold
(DEBUG, WARN, etc.) I've written two set-log-level! functions which do
this, at http://www.paullegato.com/blog/setting-clojure-log-level/ .
I'm not sure why
