unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Cc: Stefan Kangas <stefan@marxist.se>, 43949@debbugs.gnu.org
Subject: bug#43949: Strange behaviour for linum-mode
Date: Tue, 13 Oct 2020 09:30:49 +0200	[thread overview]
Message-ID: <m2mu0qlh06.fsf@gmail.com> (raw)
In-Reply-To: <CAO48Bk-5THuP-7ofiu7hAjC62Nqyd+EJ1FsByz6q+kAmeHagmA@mail.gmail.com> (Pedro Andres Aranda Gutierrez's message of "Tue, 13 Oct 2020 07:33:26 +0200")

>>>>> On Tue, 13 Oct 2020 07:33:26 +0200, Pedro Andres Aranda Gutierrez <paaguti@gmail.com> said:

    Pedro> Cool!
    Pedro> Thanks for the tip!

    Pedro> linum-format is +/-  display-line-numbers-width
    Pedro> You can control things like having a space after the line number or not a
    Pedro> little bit better

I can see how people might want that, but I think the current setup
looks good, and since the line number calculation and display runs
during redisplay, I donʼt think we want too much flexibility, as that
could slow it down.

Having said that, eliminating that space seems to work, but it does
make the display look very squashed. Eli, what do you think of
a configuration variable allowing that space to be narrower?

Robert
-- 





  reply	other threads:[~2020-10-13  7:30 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 [this message]
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

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=m2mu0qlh06.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=43949@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).