From: Michael Gallagher - NOAA Affiliate via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50506@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#50506: 28.0.50; display-line-numbers equivalent for linum-format?
Date: Mon, 13 Sep 2021 11:54:59 -0600 [thread overview]
Message-ID: <CA+e+kb1LPeJ3kR+yf3AdcX6V1EFm4y=amTt=05hBs1TtUFqonQ@mail.gmail.com> (raw)
In-Reply-To: <87tuirnwu0.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
Thank you all for the replies.
Lars, I do this already but it only really helps most when it's high
contrast (white --> black) like you've shown here. And with that, it hurts
my brain for other reasons... I swear I'm not overly sensitive.
Eli, as far as your suggestions, these requirements make sense to me. I
took a crack at modifying xdisp.c and was able to display ascii characters
by appending to lnum_buf before the numbers are displayed. However, when I
tried to hook that into the lisp code and add a variable so that it
wouldn't be hardcoded (a must, of course) I fell flat on my face.
Converting between character lisp variables to the appropriate C types is
above my "undergrad CSCI refresher" pay grade. I wish I could be more
helpful but if I were to be the one to submit a pull request I would
probably need someone to hold my hand.
Best,
Michael
On Sat, Sep 11, 2021 at 6:03 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Michael Gallagher - NOAA Affiliate <michael.r.gallagher@noaa.gov>
> writes:
>
> > The purpose for me is to clearly delineate the
> > text/code from the line numbers in a way that makes it easier to grok the
> > text being displayed. My brain sees the numbers as part of the code with
> the
> > current formatting of display-line-numbers, but maybe I'm uniquely
> > incapable.
>
> Does it help to customize the `line-number' face to something that has a
> different background colour than the main text? For instance, setting
> the background colour to black gives me this:
>
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
--
Michael Gallagher, PhD
CIRES Research Scientist
Polar Observations and Processes Team (ESRL/NOAA/PSD)
325 Broadway, Boulder, Colorado 80305
[-- Attachment #2: Type: text/html, Size: 2894 bytes --]
next prev parent reply other threads:[~2021-09-13 17:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 7:40 bug#50506: 28.0.50; display-line-numbers equivalent for linum-format? Michael Gallagher (CIRES/NOAA) via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-10 12:30 ` Eli Zaretskii
2021-09-10 16:00 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-11 11:53 ` Eli Zaretskii
2021-09-11 12:03 ` Lars Ingebrigtsen
2021-09-13 17:54 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-09-13 18:05 ` Eli Zaretskii
2021-09-13 18:17 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-13 18:27 ` Eli Zaretskii
2021-09-14 16:17 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-14 17:24 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-14 17:35 ` Eli Zaretskii
2021-09-15 15:22 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 15:49 ` Eli Zaretskii
2021-09-15 16:08 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 16:26 ` Eli Zaretskii
2021-09-15 16:45 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 16:53 ` Eli Zaretskii
2021-09-15 17:32 ` Michael Gallagher - NOAA Affiliate via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-15 18:10 ` Eli Zaretskii
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='CA+e+kb1LPeJ3kR+yf3AdcX6V1EFm4y=amTt=05hBs1TtUFqonQ@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=50506@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=michael.r.gallagher@noaa.gov \
/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).