From: Eli Zaretskii <eliz@gnu.org>
To: Alan Third <alan@idiocy.org>
Cc: 18390@debbugs.gnu.org
Subject: bug#18390: 24.4.50; REGRESSION: `split-window' error
Date: Sat, 01 Oct 2016 18:44:50 +0300 [thread overview]
Message-ID: <83lgy8kr9p.fsf@gnu.org> (raw)
In-Reply-To: <20161001130144.GA39607@breton.holly.idiocy.org> (message from Alan Third on Sat, 1 Oct 2016 14:01:44 +0100)
> Date: Sat, 1 Oct 2016 14:01:44 +0100
> From: Alan Third <alan@idiocy.org>
> Cc: Drew Adams <drew.adams@oracle.com>, 18390@debbugs.gnu.org
>
> On Sat, Oct 01, 2016 at 10:44:46AM +0300, Eli Zaretskii wrote:
> > The backtrace shows that this is the reason for signaling the error:
> >
> > split-window(#<window 8 on Palette (Hue x Saturation)> 100 t)
> >
> > This requests to split an 80-column window while leaving the original
> > window 100 columns, which is clearly impossible. So why is this a
> > bug in Emacs and not in palette.el?
>
> I can’t see how you know it’s an 80 column window, could you explain
> it to me?
The default width of an Emacs window displayed by "emacs -Q" is 80
columns. And that is the width of a window I see when I repeat Drew's
recipe and get the same error signaled as in his report.
> Looking at the code in palette.el, it requests a 115 character wide
> frame, is it possible that Emacs will return a smaller than requested
> frame?
I don't really know what palette.el is doing, but it could be that it
doesn't let the Emacs frame time to resize itself before splitting the
window.
In any case, I once again ask the question: why should we assume it's
a bug in Emacs, and not first try looking into what palette.el does?
>
> (make-frame
> `((menu-bar-lines . 0) (tool-bar-lines . 0) (left-fringe . 0) (right-fringe . 0)
> (fringe . 0) (height . 100) (width . 115) (minibuffer) (vertical-scroll-bars)
> (cursor-type . box) (background-color . "Black") (mouse-color . "Black")
> (cursor-color . "Black") ,(cons 'font palette-font)))
>
> If it is then it’s up to palette.el to check what size of frame it
> actually got back before trying to split the windows.
Actually, adding a (sit-for 0) might be all that's needed, if this is
the problem (which I'm not at all sure).
next prev parent reply other threads:[~2016-10-01 15:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 18:33 bug#18390: 24.4.50; REGRESSION: `split-window' error Drew Adams
2014-09-02 21:44 ` Drew Adams
2016-09-30 20:58 ` Alan Third
2016-09-30 21:12 ` Drew Adams
2016-09-30 21:33 ` Noam Postavsky
2016-09-30 22:39 ` Drew Adams
2016-10-01 0:12 ` npostavs
2016-10-01 0:43 ` Drew Adams
2016-10-01 7:46 ` Eli Zaretskii
2016-10-02 21:03 ` Drew Adams
2016-10-01 7:44 ` Eli Zaretskii
2016-10-01 13:01 ` Alan Third
2016-10-01 15:44 ` Eli Zaretskii [this message]
2016-10-01 16:20 ` Alan Third
2016-10-02 21:03 ` Drew Adams
2016-10-02 22:33 ` Drew Adams
2016-10-03 6:39 ` Eli Zaretskii
2016-10-03 18:34 ` Noam Postavsky
2016-10-03 19:42 ` Drew Adams
2016-10-04 20:52 ` Noam Postavsky
2016-10-04 20:58 ` Drew Adams
2016-10-04 21:15 ` Noam Postavsky
2016-10-04 23:19 ` Drew Adams
2022-04-26 12:54 ` bug#18390: [w32] " Lars Ingebrigtsen
2022-05-25 12:16 ` Lars Ingebrigtsen
[not found] ` <<901673d8-75c2-494f-956d-9f938a8e87b4@default>
[not found] ` <<83a8eoms29.fsf@gnu.org>
2016-10-02 21:03 ` bug#18390: " Drew Adams
2016-10-03 6:16 ` 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=83lgy8kr9p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18390@debbugs.gnu.org \
--cc=alan@idiocy.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 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).