emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#3301: closed (23.0.93; menu bar bug with gtk-qt en


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#3301: closed (23.0.93; menu bar bug with gtk-qt engine (KDE))
Date: Fri, 05 Jul 2019 18:03:01 +0000

Your message dated Fri, 5 Jul 2019 20:01:47 +0200
with message-id <CADwFkmkizF5ug-9NO3B4_sCPR4qjEddhxZSuWoQ0UPc=address@hidden>
and subject line Re: bug#3301: 23.0.93; menu bar bug with gtk-qt engine (KDE)
has caused the debbugs.gnu.org bug report #3301,
regarding 23.0.93; menu bar bug with gtk-qt engine (KDE)
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
3301: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3301
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.0.93; menu bar bug with gtk-qt engine (KDE) Date: Fri, 15 May 2009 23:54:03 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.93 (gnu/linux)
When the Emacs frame is not in focus on the desktop and then I bring it
into focus by clicking with the mouse pointer on the Emacs menu bar, but
to the right of any menu bar entry, this sometimes causes the menu bar
to become "active", as when I click directly on a menu bar entry; e.g. I
can navigate the menu bar with the arrow keys, and the keyboard is
otherwise unresponsive, except for ESC, and either typing this key or
clicking again with the mouse is the only way to "deactivate" the menu
bar and release the rest of the keyboard.  This behavior also happens,
though less frequently, by switching focus to Emacs with the window
manager key combination Alt-Q.  I haven't found a recipe for reproducing
this at will.  I have only gotten this behavior under KDE (both 3.5.10
and 3.4.2) with the gtk-qt engine.  I cannot say when I first saw this
behavior, but I'm pretty sure it wasn't too long ago, certainly well
into the pretest.

In GNU Emacs 23.0.93.2 (i686-pc-linux-gnu, GTK+ Version 2.14.4)
 of 2009-05-15 on escher
Windowing system distributor `The X.Org Foundation', version 11.0.10502000
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: @im=local
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t



--- End Message ---
--- Begin Message --- Subject: Re: bug#3301: 23.0.93; menu bar bug with gtk-qt engine (KDE) Date: Fri, 5 Jul 2019 20:01:47 +0200
Stephen Berman <address@hidden> writes:

> Thanks for reminding me about this.  I stopped regularly using the menu
> bar in Emacs a while ago and also had not been using KDE for some time,
> but recently started using it again (KDE Frameworks 5.59.0 in openSUSE),
> and checking now (in current master) with the Emacs menu bar enabled, I
> cannot reproduce the problem that clicking mouse-1 activates "move" mode
> (and it remains active after releasing mouse-1), only holding down
> mouse-1 does that.  So it seems this was only an issue with KDE 4*.  The
> other issue mentioned in my followup to my OP, that in KDE applications
> moving the mouse pointer over a menu bar item highlights it, even when
> the application window is not in focus, whereas moving the mouse pointer
> over an Emacs menu bar item does not highlight it, I still see but it's
> a minor cosmestic blemish, so as far as I'm concerned this bug can be
> closed.

Thank you for your reply.  Based on that, I'm closing this bug.

Thanks,
Stefan Kangas


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]