On 04/27/2015 at 09:24 PM, Vincent Lefevre wrote: > On 2015-04-27 20:52:15 -0400, The Wanderer wrote: > >> On 04/27/2015 at 08:44 PM, Vincent Lefevre wrote: >> >>> I completely agree. I would never do that. Writing a shell >>> function that greps out the Gtk-WARNING lines may be better. >> >> Not ideal, though, since there are (as I understand matters) often >> but not necessarily always blank lines in between these Gtk-WARNING >> lines. So either you cut out just the WARNING lines and still have >> scrolliness because of the blank lines making it through, or you >> snip out the adjacent lines and risk killing other information. (Or >> you make your script potentially quite a bit more complicated.) > > Yes, one can write a small script that also removes blank lines that > come after a Gtk-WARNING line. My brief research seems to indicate the blank line is actually printed _before_ the GTK-sourced line. Not sure how much harder that would make things, just offhand. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature