From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Menus with more items than the TTY can display
Date: Thu, 17 Oct 2013 19:38:57 +0300 [thread overview]
Message-ID: <83ob6nonry.fsf@gnu.org> (raw)
In-Reply-To: <525FADCF.5010700@gmx.at>
> Date: Thu, 17 Oct 2013 11:28:47 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: dmantipov@yandex.ru, emacs-devel@gnu.org
>
> This means that resize_mini_window is indeed the only candidate and I
> put a breakpoint there at if (!FRAME_MINIBUF_ONLY_P (f)).
>
> Now to reproduce the behavior, I start emacs in the terminal, remove the
> terminal's menu to be able to pass F10 to emacs, attach gdb to the
> terminal's emacs, provoke an end of buffer message in the terminal to
> verify that the breakpoint is reached at all, hit F10 in the terminal
> and scroll the menu. Now from the time I hit F10 until I hit it again
> the breakpoint is _not_ reached.
So something else seems to be at work here.
If you don't set resize-mini-windows to nil, but instead set
max-mini-window-height to 1, does the problem also go away?
Another idea would be to ifdef away this fragment from term.c:
if ((menu_help_message || prev_menu_help_message)
&& menu_help_message != prev_menu_help_message)
{
help_callback (menu_help_message,
menu_help_paneno, menu_help_itemno);
tty_hide_cursor (tty);
fflush (tty->output);
prev_menu_help_message = menu_help_message;
}
which disables help-echo in the menu, and see if the problem is gone
even without customizing resize-mini-windows. If it is, then stepping
into the help_callback call might tell who causes the problem.
If disabling help-echo does not make the problem go away, there's
something else that causes resizing, and perhaps you will be able to
spot that without help-echo getting in your way and obscuring the echo
area.
Btw, this all is in "emacs -Q", right? There are no customizations
involved, right?
> The following is an IMO meaningless backtrace after hitting F10 the
> second time:
I think you are right.
> So this is a complete mystery to me. Is it possible that toggling F10
> suppresses any signals from the terminal to the debugger?
I don't believe it can.
next prev parent reply other threads:[~2013-10-17 16:38 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 [this message]
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
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=83ob6nonry.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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).