From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Pedro Andres Aranda Gutierrez Newsgroups: gmane.emacs.bugs Subject: bug#51605: Fwd: [PATCH] Update themes to support mode-line Date: Wed, 8 Dec 2021 07:45:57 +0100 Message-ID: References: <83k0gi3nj4.fsf@gnu.org> <837dch3o4v.fsf@gnu.org> <83tufl260x.fsf@gnu.org> <86czm9699t.fsf@mail.linkov.net> <83a6hczevm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000002cfd3d05d29cd97c" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35260"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , 51605@debbugs.gnu.org, Juri Linkov To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Dec 08 08:03:34 2021 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 1muqzG-00092M-IX for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 08 Dec 2021 08:03:34 +0100 Original-Received: from localhost ([::1]:41704 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1muqzF-0008N8-AW for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 08 Dec 2021 02:03:33 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:36920) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1muqjG-0003en-MM for bug-gnu-emacs@gnu.org; Wed, 08 Dec 2021 01:47:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56126) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1muqjF-0000Dn-Te for bug-gnu-emacs@gnu.org; Wed, 08 Dec 2021 01:47:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1muqjF-0007vs-Pw for bug-gnu-emacs@gnu.org; Wed, 08 Dec 2021 01:47:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Pedro Andres Aranda Gutierrez Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 08 Dec 2021 06:47:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51605 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 51605-submit@debbugs.gnu.org id=B51605.163894600130466 (code B ref 51605); Wed, 08 Dec 2021 06:47:01 +0000 Original-Received: (at 51605) by debbugs.gnu.org; 8 Dec 2021 06:46:41 +0000 Original-Received: from localhost ([127.0.0.1]:39439 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1muqil-0007vA-8w for submit@debbugs.gnu.org; Wed, 08 Dec 2021 01:46:41 -0500 Original-Received: from mail-ed1-f48.google.com ([209.85.208.48]:38854) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1muqik-0007uv-0x for 51605@debbugs.gnu.org; Wed, 08 Dec 2021 01:46:30 -0500 Original-Received: by mail-ed1-f48.google.com with SMTP id x6so4953949edr.5 for <51605@debbugs.gnu.org>; Tue, 07 Dec 2021 22:46:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+GOFu8aWza3Py2KHcd34JoB2wsOOig5jNqlh80ZFC1k=; b=DemZYQ9hSLlR1IOlf+RIr4q8yEyuPKiIUpqb3lfblvbH/72x2Rgc7rwaMn9HS+jjws cPqo9Wb96lRkASlS+XVxs7/SocrslFb1lgykulEe0Bq917kL4vwRO3A0yTt3MJeVuFlv +1DLFKCnZuqlwburL4/bvy4HAeA+XwSbJcuqI1DWnSbIel69uOM0PCey8DTgcjKSsKxC /Qyd3ouyLnLdQwknG8nh+g148eJRrGQ94wRFStGaFTrPy4XsVd69WZPKqC+DhG79ru00 wn51RqrPx2rSHfpskrpq7G3sxw2d+Zo2gdlg5dYUNLn1WsYjeLgeWz4jVxiTQuaJjuRZ 2RAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+GOFu8aWza3Py2KHcd34JoB2wsOOig5jNqlh80ZFC1k=; b=TCbvHNBNEiKwSD9TWDxWhasAiYXvsvvlUfh0fOfCngKg8vsNpoDLXOxma3yo89LWL5 ldt8JDPgbLfHYDbd6M+5fsI+RMB06hQShWfix/NJPBVTF055IKFbN61tw/F0Blwzdv70 okZiVIo8bdNZpNO2FKu+yxSntrpshSRgzdO4vQ9Vch1bFwdu6AeyNp1exfmNRmEcOQis K+H+/ZJNv6SmzeubaXB+62cmdJnKkhfSC1lAWY6L6XJQFI4W8FoEfozIow5eVeIhvOjM 5j9GRvQRl17CqHPDClzFGYa7sGJ1GzA8qV+V8SaXqXKyCeIqgoA5Ld9JXP9NvP/Lul3S MAAA== X-Gm-Message-State: AOAM531bsWhuzUk/NJbClWLx8LG41lM21sp0O2jL2KT0VMAfpSCZAG+S H+zyWibfMAM7SYe2IILPazjOMLRlFecpDzPFOOo= X-Google-Smtp-Source: ABdhPJzWfk1A8nY6YCZNo05lRTmCBVaJffv78l3haps/iQpke0AXav4diHSShFus+cwZxzfEUCq8ovK+JJ3q+Ev+OQU= X-Received: by 2002:a05:6402:90c:: with SMTP id g12mr16833881edz.217.1638945983887; Tue, 07 Dec 2021 22:46:23 -0800 (PST) In-Reply-To: <83a6hczevm.fsf@gnu.org> 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:221908 Archived-At: --0000000000002cfd3d05d29cd97c Content-Type: text/plain; charset="UTF-8" Hi Eli, point taken... if it isn't the fringe, then something else. I find it more problematic to have the same face for the buffer and line numbers. And it's from the conceptual point of view that line numbers aren't buffer and therefore should have a different face by default. OK, I use a couple of themes that happen to have a shadowy background for the fringe, but I could live with anything that makes this _conceptual_ difference visible. (Just my .2c worth of experience; when I edit/correct Python exercises from my students, this visual difference helps me detecting indentation errors much quicker; my student's experience: different line number and buffer faces help them editing and therefore adopting Emacs as their editor of choice for Python and from there they explore org-mode for their short papers and presentations and they become regular users in no time ;-) ) Best, /PA On Tue, 7 Dec 2021 at 15:08, Eli Zaretskii wrote: > > From: Pedro Andres Aranda Gutierrez > > Date: Tue, 7 Dec 2021 07:23:11 +0100 > > Cc: Stefan Kangas , Eli Zaretskii , > 51605@debbugs.gnu.org > > > > you are right. An image is worth more than 1000 words ;-) > > > > Here you are. +/- the same are in the same file, with a theme I created > with ThemeCreator > > (https://mswift42.github.io/themecreator/) > > My main point for having line-number as fringe is the space between the > line number and the buffer. It's not > > just the practical side of it (i.e. identifying a space too much or > missing), it's also something more > > philosophical: i.e. the the difference between buffer and the rest. > > What happens if there's display margin between the fringe and the line > numbers? > > In any case, I don't understand why you insist on using the fringe as > the basic face here. The line numbers have nothing to do with the > fringe, and if you assume that the fringe's background will always be > a pale, shadowy color, that assumption can easily be false. E.g., in > my sessions the fringe has a very vivid color. It's a problematic > dependency. > -- Fragen sind nicht da um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler --0000000000002cfd3d05d29cd97c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Eli,

point taken... if it= isn't the fringe, then something else. I find it more problematic to h= ave the same face for the buffer and line numbers.
And it= 9;s from the conceptual point of view that line numbers aren't buffer a= nd therefore should have a different face by default.

<= div>OK, I use a couple of themes that happen to have a shadowy background f= or the fringe, but I could live with anything that makes this _conceptual_ = difference visible.

(Just my .2c worth of exp= erience; when I edit/correct Python exercises from my students, this visual= difference helps me detecting indentation errors much quicker; my student&= #39;s experience: different line number and buffer faces help them editing = and therefore adopting Emacs as their editor of choice for Python and from = there they explore org-mode for their short papers and presentations and th= ey become regular users in no time ;-) )

Best,= /PA

On Tue, 7 Dec 2021 at 15:08, Eli Zaretskii <eliz@gnu.org> wrote:
> From: Pedro Andres Aranda Gutierrez &= lt;paaguti@gmail.com= >
> Date: Tue, 7 Dec 2021 07:23:11 +0100
> Cc: Stefan Kangas <stefan@marxist.se>, Eli Zaretskii <eliz@gnu.org>, 51605@debbugs.gnu.org
>
> you are right. An image is worth more than 1000 words ;-)
>
> Here you are. +/- the same are in the same file, with a theme I create= d with ThemeCreator
> (https://mswift42.github.io/themecreator/)
> My main point for having line-number as fringe is the space between th= e line number and the buffer. It's not
> just the practical side of it (i.e. identifying a space too much or mi= ssing), it's also something more
> philosophical: i.e. the the difference between buffer and the rest.
What happens if there's display margin between the fringe and the line<= br> numbers?

In any case, I don't understand why you insist on using the fringe as the basic face here.=C2=A0 The line numbers have nothing to do with the
fringe, and if you assume that the fringe's background will always be a pale, shadowy color, that assumption can easily be false.=C2=A0 E.g., in<= br> my sessions the fringe has a very vivid color.=C2=A0 It's a problematic=
dependency.


--
Fragen sin= d nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu= werden
Georg Kreisler
--0000000000002cfd3d05d29cd97c--