From: Anders Rydvall <anders@rydvall.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 37007@debbugs.gnu.org
Subject: bug#37007: Problem with the menu-bars in mode "org" and "auctex"
Date: Wed, 21 Aug 2019 13:08:43 +0200 [thread overview]
Message-ID: <da0ac0a4-7712-964e-940c-4c8d0fe0937f@rydvall.com> (raw)
In-Reply-To: <f327a5f5-cdcf-09d4-1095-05f70849d236@gmx.at>
Martin!
Dragging the mouse was one, of different, ways to test. Of course I
normally don't drag the mouse.
Hitting F10 invokes the correct and complete menus in the different
modes. Moreover a new mode does not any longer seem to inherit menus
from the previous used buffer. When shifting between buffers it is
necessary to hit F10 again to get complete menus.
The F10 command seems to correctly load the menus which does not happen
only by shifting into a certain buffer. Thus there must be some problem
with the invocation of the menus. However I'm, for the moment, more
happy. I can use Emacs. Hopefully the problem will be solved in a future
version.
Regards
Anders
Den 2019-08-21 kl. 09:37, skrev martin rudalics:
> > Yes, I meant "dragging" the mouse.
>
> Why on earth would you "drag" the mouse in order to pick a menu entry?
> I'm not aware of any menu entries that change their semantics when
> dragging an object on them. What happens when you hit <f10> and use the
> keyboard to select a menu item?
>
> > When starting emacs -Q I cant see any different behavior. Invoking
> > dired with C-x d or M-x dired give the same result - incomplete
> > menues as shown in dired1. However "dragging" the mouse opens the
> > menues shown in dired2.
>
> Maybe you should indeed try to downgrade Emacs to see if the problem
> is related to the current version. Provided you can do that ...
>
> martin
next prev parent reply other threads:[~2019-08-21 11:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-11 14:31 bug#37007: Problem with the menu-bars in mode "org" and "auctex" Anders Rydvall
2019-08-12 8:59 ` martin rudalics
[not found] ` <812b33b4-5a21-302b-9791-a3c00f21c7b7@rydvall.com>
[not found] ` <6667a28d-c2f4-0476-62ba-9fda510bf32b@gmx.at>
[not found] ` <b77b67a5-6ee6-1762-ee15-5ea5510353b4@rydvall.com>
2019-08-14 9:19 ` martin rudalics
2019-08-14 11:34 ` Anders Rydvall
2019-08-15 8:12 ` martin rudalics
[not found] ` <f9604ae8-d702-db7d-ea80-321cb6e6c681@rydvall.com>
2019-08-17 8:24 ` martin rudalics
2019-08-19 11:38 ` Anders Rydvall
2019-08-21 7:37 ` martin rudalics
2019-08-21 11:08 ` Anders Rydvall [this message]
2019-08-22 8:07 ` martin rudalics
2019-08-22 12:00 ` Anders Rydvall
2019-08-23 7:45 ` martin rudalics
2022-04-30 16:59 ` Lars Ingebrigtsen
2022-05-29 13:19 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=da0ac0a4-7712-964e-940c-4c8d0fe0937f@rydvall.com \
--to=anders@rydvall.com \
--cc=37007@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).