[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44167: 28.0.50; Menu Misbehavior
From: |
Rustom Mody |
Subject: |
bug#44167: 28.0.50; Menu Misbehavior |
Date: |
Mon, 2 Nov 2020 17:38:54 +0530 |
On Mon, Oct 26, 2020 at 11:54 PM martin rudalics <rudalics@gmx.at> wrote:
>
> > I cannot reproduce this, either. I guess people are right: this is
> > specific to GTK 2.x.
>
> Here it works with GTK+ Version 2.24.32.
Couple of responses:
>From a detached impersonal perspective
Oho that muddies the waters!
Earlier it looked like a gtk 2.x problem; removed in 3.x on
Now it looks like gtk 2.24.31 has the bug and gtk 2.24.32 doesnt
So if the problem is between those it seems a hair-breath!
Else its elsewhere ie gtk is being wrongly blamed
>From my personal perspective
Please close the bug!
Multiple reasons
1. Ive got a bug-fix (well a bug-duct-tape!): Press F10 twice and the
menus get set right
2. My laptop is old and creaky (as am I!) and I'm unlikely to be able
to cooperate if I'm offered bug-fixes that involve big (re)builds
3. When I see things like
https://emacs.stackexchange.com/questions/61389/binding-xf86cut-and-xf86copy-to-emacs-commands#comment96761_61389
and
https://emacs.stackexchange.com/questions/48561/is-there-an-x11-free-build-of-emacs-that-can-run-on-wayland-not-going-through-x
;
it would be better if going forward, Emacs support Wayland and drops
gtk2 (lucid? motif??)
No this is not an argument or even a suggestion; its just a
recognition that Im on the wrong side of history!
- bug#44167: 28.0.50; Menu Misbehavior,
Rustom Mody <=