From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: stefan@marxist.se, paaguti@gmail.com, 43949@debbugs.gnu.org
Subject: bug#43949: Strange behaviour for linum-mode
Date: Tue, 13 Oct 2020 19:58:40 +0300 [thread overview]
Message-ID: <83lfga12rj.fsf@gnu.org> (raw)
In-Reply-To: <m2362ikrlw.fsf@gmail.com> (message from Robert Pluim on Tue, 13 Oct 2020 18:39:23 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: paaguti@gmail.com, stefan@marxist.se, 43949@debbugs.gnu.org
> Date: Tue, 13 Oct 2020 18:39:23 +0200
>
> >>>>> On Tue, 13 Oct 2020 19:19:54 +0300, Eli Zaretskii <eliz@gnu.org> said:
> >> and adjusting the x-coordinate of the glyphs after the space
> >> appropriately.
>
> Eli> Did you read the comment before this code?
>
> Ah no. I guess that makes it more complicated (and I need to check my
> L2R privilege more often).
Let me put it this way: if someone can find a clever algorithm to
know, when we produce the line numbers, whether the "glyph row" will
be "reversed" or not, we will be able to implement any number of
niceties like the one discussed here, which produce asymmetric space
before and after the line number. As things are, I simply couldn't
find a solution for that (which doesn't mean it doesn't exist, just
that I'm not smart enough to come up with one).
Ideas and patches are welcome.
prev parent reply other threads:[~2020-10-13 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 11:48 bug#43949: Strange behaviour for linum-mode Pedro Andres Aranda Gutierrez
2020-10-12 13:00 ` Stefan Kangas
2020-10-12 17:11 ` Pedro Andres Aranda Gutierrez
2020-10-12 17:24 ` Robert Pluim
2020-10-13 5:33 ` Pedro Andres Aranda Gutierrez
2020-10-13 7:30 ` Robert Pluim
2020-10-13 15:46 ` Eli Zaretskii
2020-10-13 16:06 ` Robert Pluim
2020-10-13 16:19 ` Eli Zaretskii
2020-10-13 16:39 ` Robert Pluim
2020-10-13 16:58 ` Eli Zaretskii [this message]
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=83lfga12rj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43949@debbugs.gnu.org \
--cc=paaguti@gmail.com \
--cc=rpluim@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).