unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Alexander Miller <alexanderm@web.de>, 45620@debbugs.gnu.org
Subject: bug#45620: 28.0.50; Child frames should have their own border width and colour
Date: Sun, 3 Jan 2021 17:15:58 +0100	[thread overview]
Message-ID: <43ccff46-1d67-2300-7098-b419966dfd66@gmx.at> (raw)
In-Reply-To: <30630458-2ef4-7da9-ea28-cdb12052dba2@web.de>

 > This is an idea set off by this discussion:
 > https://github.com/Alexander-Miller/treemacs/issues/242#issuecomment-753296634
 >
 > Basically the problem is that child frames need a distinct border colour
 > to be properly visible (and just using a different background colour does
 > not look nearly as good).
 >
 > That can be achieved by customising the `internal-border' face, however
 > that face controls the appearance of the border of all frames, and as I
 > have learned there is a non-trivial amount of users who by default use a
 > large internal border as a margin for their frames. And for these users
 > the `internal-border' should have the same colour as the default
 > background.

Isn't the situation even worse than how you describe it here?  When I
customize 'internal-border' face, that affects all frames, including
those for which I have set it already via 'set-face-background'.  Which
means that whatever a package does to set that face for a specific
(child) frame, that setting is undone by a later customization.  IIUC
the discussion you refer to above arrived at the same conclusion.

 > So there is a conflict between wanting a distinct border colour for
 > child frames and using the default background for normal frames.

If I'm not mistaken we use that face for our tooltip frames too which
means one more conflict.

 > Packages can work around that individually, for example posframe accepts
 > an `internal-border-color' argument that overrides the `internal-border'
 > face frame-locally. But that still means that every package using child
 > frames needs its own user option for the child frames' border colour
 > when such matters clearly belong under the domain of the user's theme.

"clearly" is clearly too strong here.  Ultimately, the package must have
the choice and its choice should prevail (it currently doesn't).

 > I think that since child frames serve sufficiently distinct use cases
 > than normal frames it makes sense for them to have their own border
 > appearance controls.

So what should we do?  Provide a separate 'child-frame-internal-border'
face and then probably also a 'tooltip-internal-border-face'?

Customizing such a face would still override individual frame settings.
What we need is probably a strategy to avoid setting the background for
those frames that have their internal border already set.  But then we
should do that for all faces running through 'set-face-attribute'.

martin





  reply	other threads:[~2021-01-03 16:15 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 [this message]
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
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=43ccff46-1d67-2300-7098-b419966dfd66@gmx.at \
    --to=rudalics@gmx.at \
    --cc=45620@debbugs.gnu.org \
    --cc=alexanderm@web.de \
    /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).