On Sat, Oct 29, 2016 at 3:23 AM, Carsten Haitzler <ras...@rasterman.com> wrote: > On Sat, 29 Oct 2016 01:50:21 -0200 Gustavo Sverzut Barbieri > <barbi...@gmail.com> said:
[snip] >> agreed, that's why it's nice to know if it was done in a thread or not. >> >> as for long lines, we already have separate vars that disable a big >> part of it... maybe offer an EINA_LOG_SHORTLINE=1 that disables them >> all? > > that makes sense. making thread info optional but the rest all there by > default > makes no sense to me. having a "short line" that maybe just reports filename > +line number would be useful (that's enough to track it down in most cases). > remove the full path from the file too- just the last file after the last / if > there are /'s. :) > > and maybe a minimal which is just "ERR: xxx" where xxx is the log string > content and no file/line/process etc. > > but thread info imho belongs together with pid and other such info anyway.:) Considering that reproducing can be very difficult sometimes, I rather have the maximum information possible and deal with "pollution" later. > -- > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > The Rasterman (Carsten Haitzler) ras...@rasterman.com Regards, -- Felipe Magno de Almeida ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
