From: Glenn Morris <rgm@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 447@emacsbugs.donarmstrong.com
Subject: bug#447: last-nonmenu-event and sub-menus
Date: Fri, 09 Jan 2009 15:01:53 -0500 [thread overview]
Message-ID: <0mocygdz9q.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4960B4AE.9070706@gmx.at> (martin rudalics's message of "Sun, 04 Jan 2009 14:07:58 +0100")
martin rudalics wrote:
> Glenn, just for fun please try the attached patch. It seems to solve
> your problem here but I have no idea whether it has any detrimental
> side-effects.
Yes, it seems to fix the problem, thank you.
next prev parent reply other threads:[~2009-01-09 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 13:07 bug#447: last-nonmenu-event and sub-menus martin rudalics
2009-01-09 20:01 ` Glenn Morris [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-08 22:41 Chong Yidong
2008-10-09 16:55 ` Glenn Morris
2008-06-18 23:06 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=0mocygdz9q.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=447@emacsbugs.donarmstrong.com \
--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).