From: martin rudalics <rudalics@gmx.at>
To: Live System User <nyc4bos@aol.com>, 33417@debbugs.gnu.org
Subject: bug#33417: display-buffer problems
Date: Sun, 18 Nov 2018 10:25:26 +0100 [thread overview]
Message-ID: <5BF13006.8030300@gmx.at> (raw)
In-Reply-To: <87a7m76nz6.fsf@aol.com>
> In my setup (.e.g not emacs -Q):
>
> While viewing the *Help* buffer which was the only window
> on the frame, I typed "M-x list-timers"
>
> split-window: Window #<window 266 on *Messages*> too small for splitting
>
> window-normalize-window: #<window 279> is not a valid window
>
> split-window: Window #<window 505 on window.el> too small for splitting
>
> And again:
>
> Features:
> Typing the command again, I got:
>
> Each time the buffer where the "M-x list-timers" command was
> executed was *Help* and was a single window on the frame.
>
> g--text follows this line--
>
> "C-x 2" (split-window-below) works fine.
>
> Hi,
>
>
> I then saw:
>
>
> How can I debug this?
>
> Thanks.
Doesn't (setq debug-on-error t) give you a backtrace of the
'split-window' error?
Note that 'list-timers' usually pops up the *Disabled Command* buffer
You have invoked the disabled command list-timers.
Beware: manually canceling timers can ruin your Emacs session.
Do you want to use this command anyway?
You can now type
y to try it and enable it (no questions if you use it again).
n to cancel--don’t try the command, and it remains disabled.
SPC to try the command just this once, but leave it disabled.
! to try it, and enable all disabled commands for this session only.
dialog which might be creating the problem you see.
martin
next prev parent reply other threads:[~2018-11-18 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 3:02 bug#33417: 27.0.50; display-buffer problems yLive System User
2018-11-18 3:53 ` bug#33417: " Live System User
2018-11-18 9:25 ` martin rudalics [this message]
2018-11-18 13:30 ` Live System User
2018-11-18 19:36 ` martin rudalics
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=5BF13006.8030300@gmx.at \
--to=rudalics@gmx.at \
--cc=33417@debbugs.gnu.org \
--cc=nyc4bos@aol.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 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.