From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Menus with more items than the TTY can display
Date: Fri, 18 Oct 2013 09:55:45 +0200 [thread overview]
Message-ID: <5260E981.6020604@gmx.at> (raw)
In-Reply-To: <83eh7joda2.fsf@gnu.org>
> Also, it might be worthwhile to try this in GDB, after starting Emacs:
>
> (gdb) attach EMACS-PID
> (gdb) break update_frame_1
> (gdb) commands
> > bt
> > continue
> > end
> (gdb) continue
>
> Now open the menu and do whatever you do to trigger the problem.
I can't trigger the problem when I do that :-(
With the modified term.c I always get
Lisp Backtrace:
"x-popup-menu" (0xa92fa170)
"popup-menu" (0xa92fa6c0)
"menu-bar-open" (0xa92fac20)
"call-interactively" (0xa92faf60)
"command-execute" (0xa92fb4b8)
With term.c unmodified I alternately get
Lisp Backtrace:
"x-popup-menu" (0x617c0ba0)
"popup-menu" (0x617c10f0)
"menu-bar-open" (0x617c1650)
"call-interactively" (0x617c1990)
"command-execute" (0x617c1ee8)
and
Lisp Backtrace:
"message" (0x617bf970)
"tooltip-show-help-non-mode" (0x617bfeb0)
"tooltip-show-help" (0x617c03e8)
"x-popup-menu" (0x617c0ba0)
"popup-menu" (0x617c10f0)
"menu-bar-open" (0x617c1650)
"call-interactively" (0x617c1990)
"command-execute" (0x617c1ee8)
martin
next prev parent reply other threads:[~2013-10-18 7:55 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 11:28 Menus with more items than the TTY can display Eli Zaretskii
2013-10-11 11:40 ` Dmitry Antipov
2013-10-11 14:43 ` Eli Zaretskii
2013-10-11 17:06 ` chad
2013-10-11 17:48 ` Eli Zaretskii
2013-10-14 15:38 ` Eli Zaretskii
2013-10-15 18:28 ` martin rudalics
2013-10-15 19:04 ` Eli Zaretskii
2013-10-16 7:44 ` martin rudalics
2013-10-16 15:19 ` Eli Zaretskii
2013-10-16 17:45 ` martin rudalics
2013-10-16 18:15 ` Eli Zaretskii
2013-10-16 18:34 ` martin rudalics
2013-10-16 18:59 ` Eli Zaretskii
2013-10-17 9:27 ` martin rudalics
2013-10-17 16:21 ` Eli Zaretskii
2013-10-17 17:11 ` martin rudalics
2013-10-17 17:41 ` Eli Zaretskii
2013-10-17 18:01 ` martin rudalics
2013-10-17 18:08 ` chad
2013-10-18 7:54 ` martin rudalics
2013-10-17 20:04 ` Eli Zaretskii
2013-10-18 7:54 ` martin rudalics
2013-10-17 22:52 ` Xue Fuqiao
2013-10-18 7:02 ` Eli Zaretskii
2013-10-18 7:59 ` martin rudalics
2013-10-18 22:59 ` Xue Fuqiao
2013-10-19 7:43 ` Eli Zaretskii
2013-10-19 22:51 ` Xue Fuqiao
2013-10-20 2:44 ` Eli Zaretskii
2013-10-18 7:56 ` martin rudalics
2013-10-18 9:51 ` Eli Zaretskii
2013-10-16 19:05 ` Eli Zaretskii
2013-10-17 9:28 ` martin rudalics
2013-10-17 16:38 ` Eli Zaretskii
2013-10-17 17:13 ` martin rudalics
2013-10-17 17:45 ` Eli Zaretskii
2013-10-17 18:01 ` martin rudalics
2013-10-17 20:06 ` Eli Zaretskii
2013-10-17 20:25 ` Eli Zaretskii
2013-10-18 7:55 ` martin rudalics [this message]
2013-10-18 9:32 ` Eli Zaretskii
2013-10-18 14:35 ` martin rudalics
2013-10-18 15:30 ` Eli Zaretskii
2013-10-18 19:17 ` Eli Zaretskii
2013-10-19 10:38 ` martin rudalics
2013-10-19 11:54 ` Eli Zaretskii
2013-10-19 13:57 ` martin rudalics
2013-10-19 14:57 ` Eli Zaretskii
2013-10-19 16:23 ` Eli Zaretskii
2013-10-19 18:36 ` martin rudalics
2013-10-19 19:15 ` Eli Zaretskii
2013-10-20 10:20 ` martin rudalics
2013-10-20 16:38 ` Eli Zaretskii
2013-10-20 18:41 ` martin rudalics
2013-10-20 19:16 ` Eli Zaretskii
2013-10-19 18:36 ` martin rudalics
2013-10-19 19:14 ` Eli Zaretskii
2013-10-20 10:19 ` martin rudalics
2013-10-20 16:19 ` Eli Zaretskii
2013-10-20 18:41 ` martin rudalics
2013-10-20 19:27 ` Eli Zaretskii
2013-10-21 7:19 ` martin rudalics
2013-10-21 16:42 ` Eli Zaretskii
2013-10-21 17:34 ` martin rudalics
2013-10-21 18:17 ` Eli Zaretskii
2013-10-18 7:55 ` martin rudalics
2013-10-18 9:50 ` Eli Zaretskii
2013-10-18 14:36 ` martin rudalics
2013-10-18 8:36 ` Eli Zaretskii
2013-10-18 14:35 ` martin rudalics
2013-10-11 11:41 ` Dani Moncayo
2013-10-11 12:07 ` Dmitry Antipov
2013-10-11 14:44 ` Eli Zaretskii
2013-10-11 17:49 ` Stefan Monnier
2013-10-11 18:00 ` Eli Zaretskii
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=5260E981.6020604@gmx.at \
--to=rudalics@gmx.at \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).