Comments on: Too much information! http://www.texdev.net/2009/02/26/too-much-information/ Coding in the TeX world Mon, 08 Mar 2010 14:08:06 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: DE-TeX-FAQ, DTK 1/2009, Baskerville, marginnote, splitindex, TeX at 30, Neuerscheinung, silence, TeX Pearls, Software-Updates « TeX & Friends http://www.texdev.net/2009/02/26/too-much-information/comment-page-1/#comment-197 DE-TeX-FAQ, DTK 1/2009, Baskerville, marginnote, splitindex, TeX at 30, Neuerscheinung, silence, TeX Pearls, Software-Updates « TeX & Friends Sat, 07 Mar 2009 00:08:55 +0000 http://www.texdev.net/?p=209#comment-197 [...] Wright weist in seinem Blog auf das Paket silence von Paul Isambert hin, mit dem man die Fehlermeldungen, die LaTeX beim [...] [...] Wright weist in seinem Blog auf das Paket silence von Paul Isambert hin, mit dem man die Fehlermeldungen, die LaTeX beim [...]

]]> By: Joseph Wright http://www.texdev.net/2009/02/26/too-much-information/comment-page-1/#comment-153 Joseph Wright Fri, 27 Feb 2009 22:23:24 +0000 http://www.texdev.net/?p=209#comment-153 Aditya, I'm imagine that LuaTeX might help with the console (not sure yet, but eventually), but for the log you've just got a text file. So no colour available. That's not to stop editors from colour-coding based on content (particularly if something more structured can be created in LaTeX3 or by the silence approach). Aditya, I’m imagine that LuaTeX might help with the console (not sure yet, but eventually), but for the log you’ve just got a text file. So no colour available. That’s not to stop editors from colour-coding based on content (particularly if something more structured can be created in LaTeX3 or by the silence approach).

]]> By: Joseph Wright http://www.texdev.net/2009/02/26/too-much-information/comment-page-1/#comment-152 Joseph Wright Fri, 27 Feb 2009 22:21:43 +0000 http://www.texdev.net/?p=209#comment-152 Karl, at the macro level we can deal with too much rather better than too little. The silence package is a handy addition to LaTeX2e, and hopefully the team will agree on something flexible for the LaTeX3 work. As for too little, I guess that once everything is accessible via LuaTeX you'll be able to go after everything you want too. They are changing every part of tex.web, after all! Karl, at the macro level we can deal with too much rather better than too little. The silence package is a handy addition to LaTeX2e, and hopefully the team will agree on something flexible for the LaTeX3 work.

As for too little, I guess that once everything is accessible via LuaTeX you’ll be able to go after everything you want too. They are changing every part of tex.web, after all!

]]> By: Aditya Mahajan http://www.texdev.net/2009/02/26/too-much-information/comment-page-1/#comment-149 Aditya Mahajan Fri, 27 Feb 2009 18:05:12 +0000 http://www.texdev.net/?p=209#comment-149 I sometimes wonder if it is possible for TeX to output ANSI color sequences with each message. That way, we could have packages that set the "color scheme" of the output, and can enable what gets highlighted. I sometimes wonder if it is possible for TeX to output ANSI color sequences with each message. That way, we could have packages that set the “color scheme” of the output, and can enable what gets highlighted.

]]> By: karl berry http://www.texdev.net/2009/02/26/too-much-information/comment-page-1/#comment-148 karl berry Fri, 27 Feb 2009 15:22:21 +0000 http://www.texdev.net/?p=209#comment-148 I too think there is both too little and (usually) too much logging by default. Font messages are one particular thing that come to mind; sure, tell me when something is being scaled or replaced the first time, but then after I've looked at it, I want an easy way to turn them off so I don't have to see them on every run. I've gone so far as to redefine \@font@info and \@font@warning sometimes. As for too little, the etex extensions here help, but for deepest debugging, what I often miss is the value of an argument to a primitive. TeX tells me it's executing, say, \hskip, but not what the value of the glue is. If I'm tracking down bad glue inserted somewhere, that's exactly what I want to know. However, changing this would touch virtually every part of tex.web, so I'm not holding my breath :). I too think there is both too little and (usually) too much logging by default. Font messages are one particular thing that come to mind; sure, tell me when something is being scaled or replaced the first time, but then after I’ve looked at it, I want an easy way to turn them off so I don’t have to see them on every run. I’ve gone so far as to redefine \@font@info and \@font@warning sometimes.

As for too little, the etex extensions here help, but for deepest debugging, what I often miss is the value of an argument to a primitive. TeX tells me it’s executing, say, \hskip, but not what the value of the glue is. If I’m tracking down bad glue inserted somewhere, that’s exactly what I want to know. However, changing this would touch virtually every part of tex.web, so I’m not holding my breath :) .

]]>