[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu
From: |
Po Lu |
Subject: |
bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu |
Date: |
Fri, 11 Feb 2022 19:12:55 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
> I don't see the crucial difference.
>
> From my POV, having GTK messages in *Messages* will make debugging
> Emacs's own problems harder. Some redisplay problems are only
> visible in *Messages* (because we cannot signal an error), and having
> the buffer filled up by irrelevant GTK stuff will make reading the
> messages harder, and could even make the important messages disappear,
> if the GTK stuff overflows message-log-max.
>
> So I really prefer a separate buffer.
Okay, reasonable enough, thanks.
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, (continued)
bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Robert Pluim, 2022/02/10
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Po Lu, 2022/02/10
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Eli Zaretskii, 2022/02/10
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Po Lu, 2022/02/10
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Eli Zaretskii, 2022/02/11
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Po Lu, 2022/02/11
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu, Eli Zaretskii, 2022/02/11
- bug#53916: 29.0.50; pgtk: Gtk-WARNING with popup menu,
Po Lu <=