unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Stefan Kangas <stefan@marxist.se>, 51605@debbugs.gnu.org
Subject: bug#51605: Fwd: [PATCH] Update themes to support mode-line
Date: Tue, 07 Dec 2021 10:18:10 +0200	[thread overview]
Message-ID: <86o85shpfh.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAO48Bk_v9fVmMmZkm05DiBjt+XvchQWNRifHOntOkODjhW-o5A@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Tue, 7 Dec 2021 07:23:11 +0100")

> 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.

Thanks for the images, now it's clearly seen that the problem is that
currently line numbers are displayed as part of the buffer text that
is confusing - you can't edit these numbers.  Whereas like fringes
are displayed with a darker background, it makes sense to display
line numbers with the same darker background to indicate these
numbers are not part of the buffer text.  So you patch fixes
the real problem.





  reply	other threads:[~2021-12-07  8:18 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 [this message]
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=86o85shpfh.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --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).