unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 45620@debbugs.gnu.org, Alexander Miller <alexanderm@web.de>,
	tumashu@163.com
Subject: bug#45620: 28.0.50; Child frames should have their own border width and colour
Date: Thu, 28 Jan 2021 16:35:55 +0000	[thread overview]
Message-ID: <YBLn616pvkGEtX1L@breton.holly.idiocy.org> (raw)
In-Reply-To: <1108564e-1387-36bd-a5fa-614920509b01@gmx.at>

On Thu, Jan 28, 2021 at 10:42:18AM +0100, martin rudalics wrote:
> > Is there some simple test I can try? I had a quick look through the
> > thread but didn't see anything.
> 
> Please with emacs -Q define
> 
> (defun my-make-child-frame ()
>   (interactive)
>   (make-frame
>    `((parent-frame . ,(selected-frame))
>      (undecorated . t)
>      (left . 0.5)
>      (top . 0.5)
>      (width . 0.3)
>      (height . 0.3)
>      (internal-border-width . 3))))
> 
> then do
> 
> (setq frame (my-make-child-frame))
> 
> and finally perform the following two experiments:
> 
> (1) Customize the background of the faces 'internal-border' and
> 'child-frame-border'.  Only customizing the latter should affect the
> child frame.
> 
> (2) Do
> 
> (set-frame-parameter frame 'internal-border-width 7)
> (set-frame-parameter frame 'child-frame-border-width 1)
> 
> Either of them should change the border width of the child frame as
> indicated.  If you now do
> 
> (set-frame-parameter nil 'internal-border-width 5)
> 
> with your normal frame selected, that frame's internal border width
> should change but the child frame's border width should remain
> unaltered.

That all works as I expect on macOS, so I guess we can say it's fine?

> > (GNUstep builds work for me as long as I start with a .emacs that
> > turns off the menus. I can't work out what it is that's causing the
> > problem, and even the large rewrite of some of the menu code we did on
> > the master branch makes no difference. It's quite annoying.)
> 
> I'll try turning menus off the next time.  But the number of warnings
> when building has by now exceeded any reasonable limit.  I can no more
> see the wood for the trees

Ah yes, I'd forgotten about that. As I recall the errors are mostly
from the GNUstep headers, so I don't know if they're caused by some
incompatibility between recent versions of GCC and GNUstep, or if
we're setting some compiler flag that GNUstep dislikes.

I don't get these warnings on my old Debian Jessie build environment,
just on the newer Buster one, but Jessie's really old by now.
-- 
Alan Third





  reply	other threads:[~2021-01-28 16:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 13:24 bug#45620: 28.0.50; Child frames should have their own border width and colour Alexander Miller
2021-01-03 16:15 ` martin rudalics
2021-01-04 13:38 ` Alexander Miller
2021-01-04 16:22   ` martin rudalics
2021-01-04 17:48 ` Alexander Miller
2021-01-04 18:54   ` martin rudalics
2021-01-05 12:50 ` Alexander Miller
2021-01-05 15:33   ` martin rudalics
2021-01-05 15:34     ` martin rudalics
2021-01-06 11:32       ` Arthur Miller
2021-01-06 13:36         ` martin rudalics
2021-01-06 15:01           ` Arthur Miller
2021-01-05 16:26     ` Eli Zaretskii
2021-01-06 16:32 ` Alexander Miller
2021-01-06 18:48   ` martin rudalics
2021-01-13  9:17 ` Alexander Miller
2021-01-13 18:07   ` martin rudalics
2021-01-25 12:08 ` Alexander Miller
2021-01-25 19:05   ` martin rudalics
2021-01-26 15:59     ` martin rudalics
2021-01-27 20:49       ` Alan Third
2021-01-28  9:42         ` martin rudalics
2021-01-28 16:35           ` Alan Third [this message]
2021-01-29  7:51             ` martin rudalics
2021-01-27 20:44 ` Alexander Miller
2021-01-28  3:33   ` Eli Zaretskii
2021-01-28  7:06 ` Alexander Miller

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=YBLn616pvkGEtX1L@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=45620@debbugs.gnu.org \
    --cc=alexanderm@web.de \
    --cc=rudalics@gmx.at \
    --cc=tumashu@163.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).