From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Re: About the :distant-foreground face attribute Date: Tue, 14 Jan 2014 10:47:14 -0800 Message-ID: <52D58632.3010106@dancol.org> References: <87bnzo9cja.fsf@gnu.org> <59B7E7FC-48D0-4737-B1BB-FFAC5BA9E07A@swipnet.se> <874n5f3162.fsf@gnu.org> <83fvozf86g.fsf@gnu.org> <87r48javwe.fsf@gnu.org> <83bnzmfjxe.fsf@gnu.org> <52D3E689.6050902@dancol.org> <8E16225F-53EF-498A-AB35-66EB9B33B859@swipnet.se> <52D43360.6050605@dancol.org> <9BD01B88-AF13-44DD-8DBE-4598BAC136DD@swipnet.se> <52D45C73.6090906@dancol.org> <52D4EBA9.8050802@swipnet.se> <52D4F2C2.8080800@dancol.org> <52D504A7.80104@swipnet.se> <52D514FF.7010404@dancol.org> <52D52312.6070106@swipnet.se> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1389725246 2188 80.91.229.3 (14 Jan 2014 18:47:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 14 Jan 2014 18:47:26 +0000 (UTC) Cc: Eli Zaretskii , Chong Yidong , emacs-devel To: "Jan D." Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 14 19:47:33 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W391Q-0003zz-Vn for ged-emacs-devel@m.gmane.org; Tue, 14 Jan 2014 19:47:33 +0100 Original-Received: from localhost ([::1]:50126 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W391Q-0001Nb-Jv for ged-emacs-devel@m.gmane.org; Tue, 14 Jan 2014 13:47:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W391M-0001NQ-8Z for emacs-devel@gnu.org; Tue, 14 Jan 2014 13:47:29 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W391L-00084b-0N for emacs-devel@gnu.org; Tue, 14 Jan 2014 13:47:28 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:57684) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W391H-00082v-AS; Tue, 14 Jan 2014 13:47:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=Vp/+xqu6ya3UayPwlYFfOPbJMhf8fsnoecm6BmlLMjs=; b=p5nJ99jPMVBq+exut9C/tMYAwIc0NKXb8JrUDMRCgOlgmn2FTanWGb+1Q1Ui5plod7RcrmaSFlOVe6DVZ9Qsu56Ys3FUDqd6AKqNA3/PFY/EHS9uSulpCYj3S0srk/nfcck/SfSvIrXVvBtDYM/ofrUHPo1wH+wMJdLKGdmuMMxAm/bSeGoErqD65Xf4ELONrVP1OL5F3BLt8BgbAtqTi5Ajaid8bxP/GHSjASPC8oVSW6bXT3TdnkGYIjF4wSddaIp/DNdmmzSpgozdR3MkZ3kkJzEbUxgBPXlXbuxkrZ41jP3QjNlhuNNODVOSagezrNp6ooeZzyH+Z/erfBXm8g==; Original-Received: from [2601:8:b200:217:863a:4bff:fec8:e538] by dancol.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1W391G-0002eD-1F; Tue, 14 Jan 2014 10:47:22 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 In-Reply-To: <52D52312.6070106@swipnet.se> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:168380 Archived-At: On 01/14/2014 03:44 AM, Jan D. wrote: > Daniel Colascione skrev 2014-01-14 11:44: >> On 01/14/2014 01:34 AM, Jan D. wrote: >>>>> Given the use case at hand, we know for a fact that the background is >>>>> the region background, so I don't understand why a calculated >>>>> foreground >>>>> is needed. Just pick one that matches the background. >>>>> There might be other use cases where a calculated foreground makes >>>>> sense, but my imagination fails me here. >>>> >>>> Calculated foreground colors look better: they resemble the font-lock >>>> colors on which they're based. >>> >>> For the region case, that would imply the possibility of different >>> foregrounds for marked text, none which is the actual font-lock color. >> >> It *is* the same color in the sense that the code we generate has the >> same hue. How on earth is that worse than changing arbitrary font-locked >> pieces of text to the system selection foreground color? > > Because the system color foreground is (presumably) choosen to look good > together with the system color background. Yes, and a color we algorithmically generate from a font-lock face will *also* look good against that background color, but 1) will be distinct from other faces replaced for lack of contrast, and 2) will be visually similar to the pre-highlight face. Have you tried the patch? >> But that's exactly what >> happens when we put gtk_selection_bg_color in a color spec! Why are you >> fine with allowing gtk_selection_bg_color as a color (producing a color >> that's presumably workable but unknown to a theme writer) but adamantly >> opposed to a feature that selects good colors another way? > > I'm objecting to having the system default colors replaced with > generated colors for the default case. What themes other than the > default does is irrelevant. We are just talking about defaults here. We already replace the system default colors with colors from font-lock faces. >> I've produced working code that allows Emacs to act how you prefer *and* >> how I prefer based on user configuration. What is your problem with that >> code? > > I have no problem with the code, just the defaults. > >> Have you responded to the numerous objections to >> :distant-foreground with anything other than retrenchment? > > So far the objections have been mostly opinions. If there was a > concrete case or a bug it exposes that would be another issue. > The most concrete objection is the case of inheriting faces Yidong > brought up in another mail, which indeed is a real problem. Problems with usability in UI or API design don't result in clear "bugs" in the same way that logic errors or crashes do. Fixing them relies on judgment, and that relies chiefly on informed opinion. You can't dismiss others' opinions about this feature while not subjecting your own to the same treatment. >> And a theme designer can opt not to use the feature or to explicitly >> turn it off --- but a theme designer should never have to bother, >> because the feature only activates when the contrast is awful, which >> happens only when a theme designer screws up or deliberately relies on >> system colors. > > Why should a theme designer rely on system colors? That does not sound > like a good theme. Again, the default should rely on system colors, not > arbitrary themes. You are not responding to the point I make in the text you quote. I don't know why a theme designer would use system colors either. That's not the point. I'm saying that explicitly-chosen themes should never trigger the code under discussion if they're well-designed. >>> That is not a use case. A use case describes what an actual user does >>> and in what situation automatically calculates colors enters the >>> picture. >> >> This entire thread describes the use case. There are abundant examples. >> Your objection here is baseless. > > There is a lot of handwaving and describing of mechanisms, but not one > real world example, i.e. what major mode and which font lock faces and > possible other faces are involved, and what does the user do to trigger > the generated color. Message-ID: <52D4A23E.4030802@dancol.org> From: Daniel Colascione > So to put the discussion in more concrete terms: say I run a stock > GTK3 Emacs on a system with a background color exactly equal to > "Blue1", which is the color we use for font-lock-function-name-face. > I visit xfaces.c, search for "UNSPECIFIEDP", and hit C-a C-SPC C-e. > What colors do you propose we use for the text "UNSPECIFIEDP" on that > line? > >>>> :distant-foreground has far too narrow a justification to warrant being >>>> a face property by itself. >>> >>> Also, just an opinion, not based on some documented design rule in any >>> Emacs or GNU document. >> >> So only GNU documents count now, not reasoned arguments? > > No, but if documentation of some design rule existed it would give > weight to your argument. But your statement about :distant-foreground > being too narrow is just your personal opinion which you have not > motivated with any reasoned argument, just asserted. I'm not the only one who's expressed concerns about the design of the feature.