unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 15575@debbugs.gnu.org
Subject: bug#15575: 24.3.50; New tty menus crash Emacs
Date: Fri, 11 Oct 2013 17:25:18 +0300	[thread overview]
Message-ID: <8361t3sx4h.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0jexwG4MMS5v=SQiamXhFuJpPJpyUa3V93QuO6eNvA0JA@mail.gmail.com>

> Date: Fri, 11 Oct 2013 14:04:13 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 15575@debbugs.gnu.org
> 
> > This was premature.  The last crash is practically the same as before
> > and happened after I reenlarged the frame to full height.  Not easily
> > reproducible I presume.
> 
> Here too: If I modify the width of the cmd console window, I get a
> crash the next I do anything menu-related.

What exactly do you mean by that?  The width of the cmd console window
cannot be made smaller on Windows, at least I cannot do that here (you
get a horizontal scroll bar below, but the dimensions of the console
buffer are unchanged).  I tried to enlarge the window by using
Properties, but saw no crash.

IOW, please provide a proper recipe to reproduce the problem, step by
step, starting with "emacs -Q -nw".





  reply	other threads:[~2013-10-11 14:25 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
2013-10-11 11:53                         ` martin rudalics
2013-10-11 12:04                           ` Dani Moncayo
2013-10-11 14:25                             ` Eli Zaretskii [this message]
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

  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=8361t3sx4h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15575@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    /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).