all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: nyc4bos@aol.com
To: martin rudalics <rudalics@gmx.at>
Cc: 10034@debbugs.gnu.org
Subject: bug#10034: 24.0.91; max-specpdl-size error
Date: Tue, 15 Nov 2011 21:59:46 -0500	[thread overview]
Message-ID: <84vcqkwz4t.fsf@aol.com> (raw)
In-Reply-To: <4EC0D740.7000707@gmx.at> (martin rudalics's message of "Mon, 14 Nov 2011 09:54:24 +0100")

martin rudalics <rudalics@gmx.at> writes:

>> C-g worked. However, other things that I did resulted in
>> "Variable binding depth exceeds max-specpdl-size" messages.
>
> In a situation like this does it help to do either
>
>   C-x 5 2 to make a new frame and delete the old one, or
>
>   C-x 1 to display only one window?
>
> If either of this makes the messages disappear, the bug could be in the
> window handling code.

I haven't gotten the message message thus far with the new Emacs Windows
zip file released yesterday (emacs-20111114-r106380-bin-i386.zip) by
Christoph Scholtes with newer window.el/window.c code.

I'll keep trying for a litle while longer to see if I can reproduce
it.

>
>> The specific error message that I listed above:
>>
>>   window-min-size-1: Variable binding depth exceeds max-specpdl-size
>>
>> occurred when I tried to `C-SPC C-h M-w' the *Message* buffer.
>
> What is this key sequence supposed to do?

It sets the mark, (mark-whole-buffer), and (kill-ring-save) of the
*Message* buffer so that I could paste it in the new Emacs instance
to send my bug report.

>
>> When I was geting different "max-specpdl-size" errors with almost
>> everything I subsequently did, I started up a new Emacs instance in
>> order to file a bug report.
>>
>> I then tried to copy the *Message* buffer from the original Emacs
>> instance that was having this problem into the new Emacs instance in
>> order to provide information for the bug report.
>>
>> I could `C-x b' (switch-to-buffer) to the *Message* buffer and a few
>> other things but most things resulted in different "max-specpdl-size"
>> warning messages.
>
> How many windows were on this Emacs frame at that time?

Two.

>
>> (BTW, I noticed that after sending a bug report and successfully
>> sending with `C-c C-c', the Bug Report Help buffer created when
>> invoking `(report-emacs-bug)' at least from the menu-bar, remains
>> visible as another (split) window.  Is that intentional?)
>
> I don't know.  Looking at the code of `report-emacs-bug' I don't see a
> call to remove a window but maybe I'm missing something.
>
> martin





  parent reply	other threads:[~2011-11-16  2:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13  4:46 bug#10034: 24.0.91; max-specpdl-size error nyc4bos
2011-11-13 10:49 ` martin rudalics
2011-11-13 23:01   ` nyc4bos
2011-11-14  8:54     ` martin rudalics
2011-11-14 14:38       ` Drew Adams
2011-11-16  2:59       ` nyc4bos [this message]
2011-11-14  1:24   ` nyc4bos
2011-11-14  8:54     ` martin rudalics
2011-11-16  3:14       ` nyc4bos
2011-11-16  3:43   ` nyc4bos
2011-11-16  4:01     ` Eli Zaretskii
2011-11-19  5:32       ` nyc4bos
2011-11-19  8:12         ` Eli Zaretskii
2011-12-09 23:48   ` bug#7658: 24.0.50; emacsclient not raising frame nyc4bos
2011-11-14 14:08 ` bug#10034: 24.0.91; max-specpdl-size error Stefan Monnier

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=84vcqkwz4t.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=10034@debbugs.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 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.