From: Stefan Kangas <stefan@marxist.se>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 3301-done@debbugs.gnu.org
Subject: bug#3301: 23.0.93; menu bar bug with gtk-qt engine (KDE)
Date: Fri, 5 Jul 2019 20:01:47 +0200 [thread overview]
Message-ID: <CADwFkmkizF5ug-9NO3B4_sCPR4qjEddhxZSuWoQ0UPc=Fk_LPQ@mail.gmail.com> (raw)
In-Reply-To: <87zlde6nic.fsf@escher.local.home>
Stephen Berman <stephen.berman@gmx.net> 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
prev parent reply other threads:[~2019-07-05 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:54 bug#3301: 23.0.93; menu bar bug with gtk-qt engine (KDE) Stephen Berman
2016-01-11 7:17 ` Alexis
2016-01-11 9:49 ` Stephen Berman
2016-03-06 14:26 ` Stephen Berman
2016-03-06 14:56 ` Jeff Trull
2016-03-06 15:50 ` Stephen Berman
2019-06-27 1:41 ` Stefan Kangas
2019-06-27 8:48 ` Stephen Berman
2019-07-05 18:01 ` Stefan Kangas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmkizF5ug-9NO3B4_sCPR4qjEddhxZSuWoQ0UPc=Fk_LPQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=3301-done@debbugs.gnu.org \
--cc=stephen.berman@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.