From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Visuwesh Newsgroups: gmane.emacs.bugs Subject: bug#55623: 29.0.50; Mention that (face-foreground 'default) can return "unspecified-fg" Date: Wed, 25 May 2022 22:52:00 +0530 Message-ID: <87o7zla5on.fsf@gmail.com> References: <87ilpub287.fsf@gmail.com> <87o7zmjd2f.fsf@yahoo.com> <87czg2aw0q.fsf@gmail.com> <83pmk14uo4.fsf@gnu.org> <878rqpbqxm.fsf@gmail.com> <83tu9dpmlv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5700"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: luangruo@yahoo.com, adam@alphapapa.net, 55623@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed May 25 19:23:15 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1ntuj4-0001Ia-Dz for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 25 May 2022 19:23:14 +0200 Original-Received: from localhost ([::1]:50792 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ntuj3-0000jk-0S for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 25 May 2022 13:23:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53106) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntuis-0000ip-6j for bug-gnu-emacs@gnu.org; Wed, 25 May 2022 13:23:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:34255) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1ntuir-0000jq-Ti for bug-gnu-emacs@gnu.org; Wed, 25 May 2022 13:23:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ntuir-0005hR-IZ for bug-gnu-emacs@gnu.org; Wed, 25 May 2022 13:23:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Visuwesh Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 25 May 2022 17:23:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55623 X-GNU-PR-Package: emacs Original-Received: via spool by 55623-submit@debbugs.gnu.org id=B55623.165349934221858 (code B ref 55623); Wed, 25 May 2022 17:23:01 +0000 Original-Received: (at 55623) by debbugs.gnu.org; 25 May 2022 17:22:22 +0000 Original-Received: from localhost ([127.0.0.1]:56385 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ntuiE-0005gT-48 for submit@debbugs.gnu.org; Wed, 25 May 2022 13:22:22 -0400 Original-Received: from mail-pl1-f193.google.com ([209.85.214.193]:35493) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ntuiB-0005g9-3a for 55623@debbugs.gnu.org; Wed, 25 May 2022 13:22:21 -0400 Original-Received: by mail-pl1-f193.google.com with SMTP id c2so19147780plh.2 for <55623@debbugs.gnu.org>; Wed, 25 May 2022 10:22:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=Vda91ljZoYGnAuE3osqJphSnSOrrZ8u+5WE8eFw+04w=; b=dNJku+VWQ4fTcb0cNtTR1hDGyxbRZpEWKnAYOyRSVEtAHygKNRKHdMmZ30HSj4+YMH j/wCSA1KeCqfq4lAzYhmyY5H0mvMrlv+ZJ5e3eRu06o/Q6Az1jgzT6KIyXN1kIuzZ3AN vb5ZbLOnpc8Jy5wnPUy5E7F7x0f24joYakjvU1Q1HidORKf3/hq+JGAZKKC8paXovPwB F8VGRiECURNkzMpo3BdvO1l8FgzoJ/qAAnv+dyuCgNhO9JZlDGXx/qj5Sem7U+Tni3Hq mJvBjrqzxr/VymB7X+GjMv43paYQXyeU6hCrX0PzNNpzptAoxexmj79mXetAPHdkZHt2 XlqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=Vda91ljZoYGnAuE3osqJphSnSOrrZ8u+5WE8eFw+04w=; b=CC1Kk+7jEGBL0Sf3iePFmlbEFu083+HcyKqbS6/cNy/podvrL4mUYKdMhHk7S5FISr No8dCcyT6dUEyXPaK7DUZ/2Los6jEZwtqGZL9aTbkHyc796fVlOF9FqlUiqwwBzz4eks wDmnJdMeD1Lmx8lkHERXgIioRYjSZ1guU3nRVJlp4R637rtvyCRSxD3uGEMTSIdxYhGb dZF/jKVSk0MU/nRH9HlMMJlCFlYvN4a/MSddNPgHhC0i2xBPJwhP6dUsEy6d+UGboHFe L028/ql/1nKiIr826q70Gy7EBFwFm0dT27DSQNIfcj0ECygincKd+eBvfGqXrdqWmCjA jU+w== X-Gm-Message-State: AOAM531H/AdHb/xHagfNXwKxkH7h6QeUrLnve5319lThSKpTvCbupYY4 HFDLYmxx1r1rAM6r7VZTdlE= X-Google-Smtp-Source: ABdhPJyUwVtJOy2/P6VGZN65ZYzEESdiRBoKFxJoAVSJcN5q5MqsyoWu88OoTb4z+cvGdTJ20gbw+w== X-Received: by 2002:a17:903:32d2:b0:161:d485:613f with SMTP id i18-20020a17090332d200b00161d485613fmr33727186plr.173.1653499333256; Wed, 25 May 2022 10:22:13 -0700 (PDT) Original-Received: from localhost ([49.205.86.52]) by smtp.gmail.com with ESMTPSA id cw25-20020a056a00451900b0050dc76281d3sm11752838pfb.173.2022.05.25.10.22.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 May 2022 10:22:12 -0700 (PDT) In-Reply-To: <83tu9dpmlv.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 May 2022 20:07:24 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:233073 Archived-At: [=E0=AE=AA=E0=AF=81=E0=AE=A4=E0=AE=A9=E0=AF=8D =E0=AE=AE=E0=AF=87 25, 2022]= Eli Zaretskii wrote: >> From: Visuwesh >> Cc: luangruo@yahoo.com, 55623@debbugs.gnu.org, adam@alphapapa.net >> Date: Wed, 25 May 2022 20:27:41 +0530 >>=20 >> > They aren't documented on purpose: documenting them would be messy and >> > at best will confuse anyone who isn't familiar with the internals of >> > color support on TTY frames. They are in effect internal >> > implementation details which unfortunately leak outside of the >> > internals. >> > >>=20 >> I agree but I think anyone who is fairly familiar with terminal >> emulators can understand that you cannot find the terminal emulator's >> colourscheme (for a lack of a better word) in a terminal-agnostic way. >> Thus, I believe there won't be too much confusion if we added such a >> text. > > Which "such text" did you have in mind? The problem here is to come > up with a useful text, which explains something without raising a lot > more questions. > The text that could be added to describe these strange colour names. >> > What would you like to be documented about these special values, and >> > why? >>=20 >> I would like it if some words along the lines of... >>=20 >> The 'default' face is always fully specified except in special cases >> of TTY frames where :foreground and :background attributes may be >> the strings "unspecified-fg" and "unspecified-bg" respectively. > > Without explaining the reason for these strange "color names", how can > this be useful to anyone? > Which is why, I said "You could also add the implementation details, but I leave the decision to you." How about the following instead then? The 'default' face is always fully specified except in special cases of TTY frames where :foreground and :background attributes may be the strings "unspecified-bg" and "unspecified-bg" respectively to mean to use the TTY's color for the foreground and background. >> As for the why: In the bug report I alluded to in the OP, ement.el >> relied on the completeness of the default-face specification to get the >> colour of the face which is then used to calculate a different colour >> (similar to the rainbow coloured nicknames you often see in irc >> clients). This special case of the TTY frame would be handled correctly >> if it was spelt out somewhere. (It isn't now since the value returned is >> a surprise.) > > In such rare cases, it is much easier to explain the issue to a person > who needs to deal with it (or thinks he/she needs to) than come up > with a description useful enough to be in the manual. > > They are just "special color names", that's all. I suppose. But I think it would be for the best if we outlined it in the manual. It comes as a "surprise" after all.