unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: paaguti@gmail.com, 51605@debbugs.gnu.org
Subject: bug#51605: Fwd: [PATCH] Update themes to support mode-line
Date: Mon, 06 Dec 2021 15:54:06 +0200	[thread overview]
Message-ID: <83tufl260x.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=zeN0rbeO6MmZAnagS+=SLxwCeP+o5XRFv18pozN93xA@mail.gmail.com> (message from Stefan Kangas on Mon, 6 Dec 2021 14:25:39 +0100)

> From: Stefan Kangas <stefan@marxist.se>
> Date: Mon, 6 Dec 2021 14:25:39 +0100
> Cc: 51605@debbugs.gnu.org, paaguti@gmail.com
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I don't see why they would be better.  They are just different.  the
> > current defaults are borrowed from linum.el, where they were used for
> > ages by many people.
> 
> I tried to explain why I think that in my previous email.  In short:
> The proposal adds functionality that is not there OOTB, but that would
> be useful to provide OOTB.

The line number is already separated from the buffer text, albeit not
by its typeface.  So I still think your proposal is merely different,
not necessarily better.  There are good reasons to have the line
numbers in the same font as the default face.

> The point is to set a precedent about the way we suggest Emacs should
> behave.

We _have_ set the precedent: this feature is available in its current
form since Emacs 26.





  reply	other threads:[~2021-12-06 13:54 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 [this message]
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
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=83tufl260x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51605@debbugs.gnu.org \
    --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).