unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: stefan@marxist.se, 51605@debbugs.gnu.org, juri@linkov.net
Subject: bug#51605: Fwd: [PATCH] Update themes to support mode-line
Date: Wed, 08 Dec 2021 15:19:07 +0200	[thread overview]
Message-ID: <83sfv3w7xw.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk-XmoSQ4UEpzzHKn6s8Epiar658t8SQ6UQM9quY5TAENw@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Wed, 8 Dec 2021 07:45:57 +0100)

> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Wed, 8 Dec 2021 07:45:57 +0100
> Cc: Juri Linkov <juri@linkov.net>, Stefan Kangas <stefan@marxist.se>, 51605@debbugs.gnu.org
> 
> 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. 

I don't think I agree with this concept.  For example, the stuff
usually written into the display margins is also separate from the
buffer text, but we still use the same 'default' face there.

> (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 ;-) )

No one argues that some situations and some personal preferences call
for a distinct face for the line numbers.  That's why we use a special
face there, not the default face.  That's not what the argument is
about.  It is about changing the defaults, and that must have reasons
much more serious than just anecdotal evidence about this or that use
case.





  reply	other threads:[~2021-12-08 13:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAO48Bk-egwN7eEoCyhcB491VzQ8QGx_oLRubZgC-0ULgDfqpAQ@mail.gmail.com>
2021-11-05  7:27 ` bug#51605: Fwd: [PATCH] Update themes to support mode-line Stefan Kangas
2021-11-05 23:24   ` Lars Ingebrigtsen
2021-11-05 23:54     ` Stefan Kangas
2021-11-06  0:17       ` Lars Ingebrigtsen
2021-11-06  0:43         ` Stefan Kangas
2021-12-05 18:05   ` Stefan Kangas
2021-12-05 18:38     ` Eli Zaretskii
2021-12-05 21:49       ` Stefan Kangas
2021-12-06  6:21         ` Pedro Andres Aranda Gutierrez
2021-12-06 13:04           ` Eli Zaretskii
2021-12-06 12:37         ` Eli Zaretskii
2021-12-06 13:25           ` Stefan Kangas
2021-12-06 13:54             ` Eli Zaretskii
2021-12-06 15:08               ` Stefan Kangas
2021-12-06 16:38                 ` Eli Zaretskii
2021-12-06 17:00                 ` Juri Linkov
2021-12-07  6:23                   ` Pedro Andres Aranda Gutierrez
2021-12-07  8:18                     ` Juri Linkov
2021-12-07 14:08                     ` Eli Zaretskii
2021-12-08  6:45                       ` Pedro Andres Aranda Gutierrez
2021-12-08 13:19                         ` Eli Zaretskii [this message]
2021-12-09  7:39                           ` Pedro Andres Aranda Gutierrez
2021-12-09 14:03                             ` Stefan Kangas
2022-09-10  4:49   ` Lars Ingebrigtsen

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=83sfv3w7xw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51605@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=paaguti@gmail.com \
    --cc=stefan@marxist.se \
    /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).