From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Q: child frames on ttys Date: Sat, 31 Aug 2024 17:40:17 +0300 Message-ID: <86cylobvse.fsf@gnu.org> References: <86ikvz302s.fsf@gnu.org> <132fd5ff-bcdf-4d93-acab-186e52f80d9a@gmx.at> <86jzfye0hf.fsf@gnu.org> <86ikvgc3gz.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27715"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rudalics@gmx.at, emacs-devel@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 31 16:41:13 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1skPHt-000741-MX for ged-emacs-devel@m.gmane-mx.org; Sat, 31 Aug 2024 16:41:13 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1skPHC-0007wO-Fw; Sat, 31 Aug 2024 10:40:30 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1skPH8-0007ut-Ly for emacs-devel@gnu.org; Sat, 31 Aug 2024 10:40:27 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1skPH8-0002KI-7j; Sat, 31 Aug 2024 10:40:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=MrHs0jpmZK8J9b7EyKtGPjZsHaf4VnBqZRhTDte/Ktk=; b=NgbJBJncpR4GFkyLu0my BUKFSVgTbVfJy6A+GZFX3pmd/5atnj9yNGNBH/dC20wGUtPQNQCF6kAmmtlFTrWkt7J4WzTW/wMs1 Go+pEllJjC5zH42hdp9SpxpBkmVLDGxXLeBmK0c17ObN6/SovvzTZ6wqs4Mg259nJlPxJAsJgWBCv w1tt5gcjlzhJlnLoESCZ5o6ylYBKpJkiVWKtLzg4hZqnRwHeO0NTMbIfsZttO/05wT0ucPS9bKnif kcoQm+EfEpoeelawKvEAaocVVYsaVfiqv01t5F1w5NEspubtjBaxOwilpXrU2lsq0jeuiw16QTigJ FIBJA+7H7q55Zw==; In-Reply-To: (message from Gerd =?utf-8?Q?M=C3=B6llmann?= on Sat, 31 Aug 2024 16:00:22 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:323239 Archived-At: > From: Gerd Möllmann > Cc: rudalics@gmx.at, emacs-devel@gnu.org > Date: Sat, 31 Aug 2024 16:00:22 +0200 > > Eli Zaretskii 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.