<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hello,<div><br></div><div>You are looking for +W flag, e.g. erl +W i should make a trick for you.</div><div><br></div><div><dt style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: inherit; background-color: rgb(255, 255, 255); position: static; z-index: auto;"><strong><span class="code" style="font-family: Courier, monospace; font-weight: normal;">+W w | i</span></strong></dt><dd style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: inherit; background-color: rgb(255, 255, 255); position: static; z-index: auto;"><p>Sets the mapping of warning messages for <span class="code" style="font-family: Courier, monospace;">error_logger</span>. Messages sent to the error logger using one of the warning routines can be mapped either to errors (default), warnings (<span class="code" style="font-family: Courier, monospace;">+W w</span>), or info reports (<span class="code" style="font-family: Courier, monospace;">+W i</span>). The current mapping can be retrieved using <span class="code" style="font-family: Courier, monospace;">error_logger:warning_map/0</span>. See <span class="bold_code" style="font-family: Courier, monospace; font-weight: bold;"><a href="http://erlang.org/doc/man/error_logger.html#warning_map-0" style="color: blue; text-decoration: none;">error_logger(3)</a></span> for further information.</p></dd><div><br></div></div><div>However, I would still advice to use lagger. It is compatible with error_logger framework and nicely cooperates with legacy code. Long time ago, I’ve passed through your dilemma, as the result. I’ve end-up with lagger.</div><div><br></div><div>BTW, I am also confused with goldrush dependencies in lager. I guess it is used to manage flow control to std io.</div><div><br></div><div>- Dmitry</div><div><br><div><div>On 03 Feb 2014, at 23:29, Niklas Semmler <<a href="mailto:semmler@kth.se">semmler@kth.se</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">The code I am working on is supposed to be integrated with a bigger system later on. As far as I know the other system uses native logging.<br><br>That's why I want to avoid Lager. I would rather work out my own get_event..<br><br>-- Niklas <br><br>On Feb 3, 2014, at 9:51 PM, Jesper Louis Andersen wrote:<br><br><blockquote type="cite">On Mon, Feb 3, 2014 at 7:20 PM, Niklas Semmler <<a href="mailto:semmler@kth.se">semmler@kth.se</a>> wrote:<br><br><blockquote type="cite">PS: Lager is unfortunately not an option as I have to avoid any<br>unnecessary dependencies.<br></blockquote><br><br>You really want lager for this. What is the rationale for avoiding an<br>unnecessary dependency?<br><br><br>-- <br>J.<br></blockquote><br>_______________________________________________<br>erlang-questions mailing list<br><a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br><a href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a><br></blockquote></div><br></div></body></html>