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: Tue, 07 Dec 2021 16:08:45 +0200 [thread overview]
Message-ID: <83a6hczevm.fsf@gnu.org> (raw)
In-Reply-To: <CAO48Bk_v9fVmMmZkm05DiBjt+XvchQWNRifHOntOkODjhW-o5A@mail.gmail.com> (message from Pedro Andres Aranda Gutierrez on Tue, 7 Dec 2021 07:23:11 +0100)
> From: Pedro Andres Aranda Gutierrez <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 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.
next prev parent reply other threads:[~2021-12-07 14:08 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 [this message]
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=83a6hczevm.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).