unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Gallagher - NOAA Affiliate <michael.r.gallagher@noaa.gov>
Cc: 50506@debbugs.gnu.org
Subject: bug#50506: 28.0.50; display-line-numbers equivalent for linum-format?
Date: Sat, 11 Sep 2021 14:53:49 +0300	[thread overview]
Message-ID: <83o88zgwfm.fsf@gnu.org> (raw)
In-Reply-To: <CA+e+kb2=RJVoHJsZB0V9tOUgahf2T_p5ZwcA=P0mFRaqe5qjGg@mail.gmail.com> (message from Michael Gallagher - NOAA Affiliate on Fri, 10 Sep 2021 10:00:47 -0600)

> From: Michael Gallagher - NOAA Affiliate <michael.r.gallagher@noaa.gov>
> Date: Fri, 10 Sep 2021 10:00:47 -0600
> Cc: 50506@debbugs.gnu.org
> 
> Thanks for taking the time to respond. The separator character I use is simply the 'pipe' character, "|". 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. 

If the intent is to provide a new user option to display such a
character after the number, I don't object.  But please note the
following subtle aspects of such a change:

  . since you'd probably want to make the character customizable, and
    non-ASCII characters are sometimes desired, there will be a need
    to make sure such a non-ASCII character can be displayed before
    honoring the customization

  . on some displays, the pipe character "|" isn't tall enough, so the
    vertical line is not contiguous

  . there's a problem with doing this for right-to-left lines, because
    the character should then be before the number, not after it, but
    (due to complicated reasons I will not describe here) when the
    line number is prepared for display, the display code doesn't
    necessarily know whether the line is R2L or L2R






  reply	other threads:[~2021-09-11 11:53 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 [this message]
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
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=83o88zgwfm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50506@debbugs.gnu.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).