Re: [lmi] GTK warnings

[Vadim Zeitlin]

On Fri, 1 Jul 2022 19:56:31 +0000 Greg Chicares <gchicares@sbcglobal.net> wrote:

GC> On 7/1/22 17:32, Vadim Zeitlin wrote:
GC> > On Fri, 1 Jul 2022 16:00:30 +0000 Greg Chicares <gchicares@sbcglobal.net> 
wrote:
GC> [...]
GC> > GC> I have the impression that GTK might be sending messages to someplace
GC> > GC> like /dev/tty .
GC> > 
GC> >  Strange, I don't see this here, i.e. if I do
GC> > 
GC> >   % ./lmi_wx 2>err.log
GC> > 
GC> > I see Gtk-CRITICIAL and other messages in the err.log file.
GC> 
GC> Yes, with lmi I often do exactly that, and it works as intended,
GC> with lmi. But with 'meld' it doesn't: even if I redirect both
GC> stdout and stderr:
GC>   >err.log 2>&1
GC> the GTK-meld messages pollute my terminal's scrollback, and
GC> create an empty log file.

 Looking at meld sources I still don't see any real explanation for this. I
could debug it if you'd really like to know the answer, please let me know.
Also, as meld is written in Python, it should be pretty trivial to hack it
to change whatever it does if you really want to.

 BTW, while looking at meld sources, I see that they just suppress "Drawing
a gadget with negative dimensions" messages unconditionally, see

https://gitlab.gnome.org/GNOME/meld/-/blob/3.21.2/bin/meld#L375

GC> But that's okay: I've learned to live with it by lowering
GC> my expectations of GTK (and wine, likewise).

 I still think we might be doing something wrong with in MDI implementation
for wxGTK, so I'm going to look into it. But I do blame GTK for outputting
scary looking CRITICAL messages for something which is not critical at all.

 Regards,
VZ

pgpF1ec_ak_Pn.pgp
Description: PGP signature