unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Alan Third <alan@idiocy.org>
Cc: 18390@debbugs.gnu.org
Subject: bug#18390: 24.4.50; REGRESSION: `split-window' error
Date: Sun, 2 Oct 2016 15:33:49 -0700 (PDT)	[thread overview]
Message-ID: <9a262a33-f1b7-40d5-afc3-2bfc6de55c6f@default> (raw)
In-Reply-To: <75deb4d8-48f0-43ef-814a-037e01190fdf@default>

[-- Attachment #1: Type: text/plain, Size: 940 bytes --]

FWIW, I've attached screenshots from my setup (not emacs -Q),
from Emacs 23.4 (which is the same as Emacs 22), Emacs 24.3,
and Emacs 24.4.

It is Emacs 24.4 that manifests the bug of this report (but
the bug is not shown in the screenshot).

You can see that already in 24.3 the black lines separating
the windows are doubly thick.

In Emacs 24.4, there is the added glitch that there is an extra
blue line in the brightness window (rightmost window).

All three screenshots show the non-bug condition of the frame.
I present them just to show that things have changed in Emacs.

I can live with the changed behavior (though I don't understand
it - in particular, the thin blue line).  I can try to debug
that separately.  But I thought it might help to show what
happens when this bug does not manifest itself, as well as to
show some of what has changed in Emacs.  The code is the same,
and is pretty straightforward.

[-- Attachment #2: throw-palette-emacs-24-3.png --]
[-- Type: image/png, Size: 19787 bytes --]

[-- Attachment #3: throw-palette-emacs-23.4.png --]
[-- Type: image/png, Size: 16877 bytes --]

[-- Attachment #4: throw-palette-emacs-24.4.png --]
[-- Type: image/png, Size: 23082 bytes --]

  reply	other threads:[~2016-10-02 22:33 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
2016-10-01 16:20           ` Alan Third
2016-10-02 21:03           ` Drew Adams
2016-10-02 22:33             ` Drew Adams [this message]
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=9a262a33-f1b7-40d5-afc3-2bfc6de55c6f@default \
    --to=drew.adams@oracle.com \
    --cc=18390@debbugs.gnu.org \
    --cc=alan@idiocy.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 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).