From: David Engster <deng@randomsample.de>
To: Glenn Morris <rgm@gnu.org>
Cc: 14021@debbugs.gnu.org
Subject: bug#14021: Activation of both Semantic and EDE disables their common submenu in main emacs menu, leaving it available only in visible menu bar
Date: Mon, 10 Feb 2014 22:59:47 +0100 [thread overview]
Message-ID: <87bnyek4rw.fsf@engster.org> (raw)
In-Reply-To: <q6d2iuveyb.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 10 Feb 2014 16:24:28 -0500")
Glenn Morris writes:
> David Engster wrote:
>
>>> * emacs -Q
>>>
>>> * M-x menu-bar-mode, so that menu-bar is disabled
>>>
>>> * M-x semantic-mode
>>>
>>> * M-x global-ede-mode
>>>
>>> * Now do C-Mouse 3 to open the "global menu" popup (which I didn't know
>>> existed until yesterday...)
>>>
>>> Look at the "Development" menu at the bottom. It might be disabled. If
>>> not, try the recipe again - it seems to be a race condition.
>>
>> I was wrong here; there's no race condition, but it depends on the order
>> of mode activation. If you *first* enable global-ede-mode and then
>> semantic-mode, the Development menu will be disabled. So to be clear:
>> the above recipe is false; you have to do 'M-x global-ede-mode' first,
>> and then do 'M-x semantic-mode'.
>
> I could not seem to reproduce this. Was it fixed?
I managed to work around it with this patch, which is also in Emacs:
http://cedet.bzr.sourceforge.net/bzr/cedet/code/trunk/revision/8507
I think there is a bug in how the global menu is handling this, but I
guess that should be a separate bug report? IOW, I'd have no problem
with closing this.
-David
next prev parent reply other threads:[~2014-02-10 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 13:37 bug#14021: Activation of both Semantic and EDE disables their common submenu in main emacs menu, leaving it available only in visible menu bar Nikita Zlobin
2013-03-22 7:51 ` David Engster
2013-03-22 17:45 ` David Engster
2014-02-10 21:24 ` Glenn Morris
2014-02-10 21:59 ` David Engster [this message]
2014-02-10 22:03 ` Glenn Morris
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=87bnyek4rw.fsf@engster.org \
--to=deng@randomsample.de \
--cc=14021@debbugs.gnu.org \
--cc=rgm@gnu.org \
/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).