unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Q: child frames on ttys
Date: Sat, 31 Aug 2024 17:40:17 +0300	[thread overview]
Message-ID: <86cylobvse.fsf@gnu.org> (raw)
In-Reply-To: <m25xrg6bd5.fsf@pro2.fritz.box> (message from Gerd Möllmann on Sat, 31 Aug 2024 16:00:22 +0200)

> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: rudalics@gmx.at,  emacs-devel@gnu.org
> Date: Sat, 31 Aug 2024 16:00:22 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> The simplest such function is of course the identity function, which
> >> means child and root share the same face cache. With the consequence
> >> that changing named faces on the child modifies faces of the root. Not
> >> nice, but simple.
> >> 
> >> As I said, I'm not sure about this. I could also think of redefining the
> >> concept of face id to something containing the frame or cache holding
> >> the face's definition. Which could be done in more than one way. And so
> >> on, but it's certainly some work.
> >> 
> >> What do people think?
> >
> > FWIW, I don't see why this would be a serious limitation.  After all,
> > by default we define the faces identically on all frames, and Lisp
> > programs that want to have different faces on different frames need to
> > actively opt in.  Most don't.
> 
> Thanks.
> 
> I think I'm mostly concerned of the seemingly harmless background-color
> frame parm, and what else there is which change the default face on a
> frame. I could imagine that one would want to do that for child frames.
> Like a frame for completion candidates, for example.

We should document that this doesn't work on TTY displays, and let
applications deal with that.

> Hm. I think I'll leave that as is for now, i.e. simply share the
> face cache with the root. It could be changed later, and it's pretty
> independent of the rest, I'd say. At least as far as I can see now.

Right.  Just please don't forget documenting it.



  reply	other threads:[~2024-08-31 14:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17  7:24 Q: child frames on ttys Gerd Möllmann
2024-08-17 10:39 ` Eli Zaretskii
2024-08-17 11:02   ` Gerd Möllmann
2024-08-17 17:18   ` martin rudalics
2024-08-17 18:41     ` Gerd Möllmann
2024-08-21  7:10       ` Gerd Möllmann
2024-08-21  7:55         ` martin rudalics
2024-08-21  8:03           ` Gerd Möllmann
2024-08-21  8:11             ` Robert Pluim
2024-08-21  8:38               ` Gerd Möllmann
2024-08-21 12:00         ` Gerd Möllmann
2024-08-30  6:42           ` Gerd Möllmann
2024-08-30  9:17             ` martin rudalics
2024-08-30 11:03               ` Eli Zaretskii
2024-08-30 11:23                 ` Gerd Möllmann
2024-08-30 14:53                   ` Eli Zaretskii
2024-08-31  8:26                 ` Gerd Möllmann
2024-08-31 11:54                   ` Eli Zaretskii
2024-08-31 14:00                     ` Gerd Möllmann
2024-08-31 14:40                       ` Eli Zaretskii [this message]
2024-09-02  8:37                         ` Gerd Möllmann
2024-09-02 11:38                           ` Eli Zaretskii
2024-09-02 12:46                             ` Gerd Möllmann
2024-09-02 13:13                               ` Eli Zaretskii
2024-09-02 13:54                                 ` Gerd Möllmann
2024-08-30 11:09               ` Gerd Möllmann
2024-08-30  9:29             ` Robert Pluim
2024-08-30 11:19               ` Gerd Möllmann
2024-08-30 12:00                 ` Robert Pluim
2024-08-30 12:37                   ` Gerd Möllmann
2024-08-30 21:11 ` Dmitry Gutov
2024-08-31  6:45   ` Eli Zaretskii
2024-08-31  8:46     ` Po Lu
2024-09-01  0:27       ` Dmitry Gutov
2024-09-16  1:35         ` Dmitry Gutov
2024-09-01  0:27     ` Dmitry Gutov

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=86cylobvse.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=rudalics@gmx.at \
    /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).