From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15575@debbugs.gnu.org
Subject: bug#15575: 24.3.50; New tty menus crash Emacs
Date: Fri, 11 Oct 2013 13:42:37 +0200 [thread overview]
Message-ID: <5257E42D.6000507@gmx.at> (raw)
In-Reply-To: <83eh7srrmu.fsf@gnu.org>
> How tall is your cmd window? Is it 25-line tall, per chance?
I don't remember but it's possible.
> If so,
> try the latest trunk, this problem should be fixed there.
With latest trunk I'm not able to produce it any more so this seems to
be fixed.
>> Since I never work with -nw I have no idea how to debug this.
>
> Because -nw takes control of the screen, or because you don't think
> you are familiar enough with the internals in the -nw case?
>
> If the former, I can tell you the tricks I use.
The former. I'm used to debug emacs from another emacs but with -nw
this seems impossible. And in a cmd.exe window emacs takes control of
the window as you say. What do you use to get back to the debugger?
A minor nitpick: When I mouse-open the Tools menu and, with that menu
open, mouse-click the Emacs-Lisp menu, the Tools menu is still around.
Any simple way to close all open menus when opening a new one?
martin
next prev parent reply other threads:[~2013-10-11 11:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 17:05 bug#15575: 24.3.50; New tty menus crash Emacs Jan Djärv
2013-10-09 17:41 ` Eli Zaretskii
2013-10-09 17:58 ` Jan Djärv
2013-10-09 18:17 ` Jan Djärv
2013-10-09 18:20 ` Jan Djärv
2013-10-09 19:00 ` Eli Zaretskii
[not found] ` <97F9A2CA-8E08-4867-93C3-5BAE8DF80D72@swipnet.se>
2013-10-10 16:15 ` Eli Zaretskii
2013-10-10 17:35 ` Jan Djärv
2013-10-10 19:36 ` Eli Zaretskii
2013-10-11 5:44 ` Jan Djärv
2013-10-11 7:09 ` Eli Zaretskii
2013-10-11 8:10 ` Eli Zaretskii
2013-10-11 9:28 ` Eli Zaretskii
2013-10-11 11:06 ` Eli Zaretskii
2013-10-11 16:39 ` Jan Djärv
2013-10-11 17:29 ` Eli Zaretskii
2013-10-11 18:53 ` Jan Djärv
2013-10-11 11:12 ` Jan Djärv
2013-10-11 9:55 ` martin rudalics
2013-10-11 11:09 ` Eli Zaretskii
2013-10-11 11:42 ` martin rudalics [this message]
2013-10-11 11:53 ` martin rudalics
2013-10-11 12:04 ` Dani Moncayo
2013-10-11 14:25 ` Eli Zaretskii
2013-10-11 14:43 ` Dani Moncayo
2013-10-11 14:54 ` Eli Zaretskii
2013-10-11 15:02 ` Dani Moncayo
2013-10-11 15:44 ` Eli Zaretskii
2013-10-11 16:37 ` Dani Moncayo
2013-10-11 14:20 ` Eli Zaretskii
2013-10-15 18:27 ` martin rudalics
2013-10-11 14:17 ` Eli Zaretskii
2013-10-11 18:22 ` Eli Zaretskii
2013-10-11 18:49 ` Stefan Monnier
2013-10-11 20:26 ` Eli Zaretskii
2013-10-15 18:27 ` martin rudalics
2013-10-15 19:01 ` Eli Zaretskii
2013-10-16 7:44 ` martin rudalics
2013-10-16 15:21 ` Eli Zaretskii
2013-10-16 17:48 ` martin rudalics
2013-10-16 18:34 ` Eli Zaretskii
2013-10-16 18:45 ` martin rudalics
2013-10-10 20:56 ` Stefan Monnier
2013-10-10 20:59 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5257E42D.6000507@gmx.at \
--to=rudalics@gmx.at \
--cc=15575@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.