From: Stefan Kangas <stefan@marxist.se>
To: Mark Lillibridge <mdl@alum.mit.edu>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 16006-done@debbugs.gnu.org
Subject: bug#16006: 24.3; *grep* fails to display line numbers with global-linum-mode
Date: Wed, 12 Aug 2020 15:34:09 -0700 [thread overview]
Message-ID: <CADwFkmk8P0r0XDoVurLFQimLETxfNVe1J5O8t5=gLBF2N_M3GQ@mail.gmail.com> (raw)
In-Reply-To: <87zjo8xup8.fsf@foil.strangled.net> (Mark Lillibridge's message of "Tue, 10 Dec 2013 13:27:47 -0800")
Mark Lillibridge <mdl@alum.mit.edu> writes:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> > Note that only the first four lines of the *grep* buffer have line
>> > numbers when all the visible lines should have line numbers. Switching
>> > to the new *grep* buffer dones make the line numbers appear.
>>
>> Indeed linum.el suffers from various corner case problems. Maybe this
>> one is fixed in Emacs trunk, or maybe it can be fixed. But the
>> implementation technique used by linum.el has proved over the years to
>> lead to many such corner case issues.
>>
>> I suggest you try out nlinum.el (available in GNU ELPA) which provides
>> basically the same functionality as linum.el but using a different
>> implementation approach, which is more robust.
>
> Very nice! Does not suffer from this bug. I will play with it
> more. Add the following in order to get a global mode:
So the solution here was to use nlinum instead of linum. We now also
have display-numbers-mode.
Since there also have been no further updates here within 6 years, I'm
closing this bug now.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-08-12 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 1:13 bug#16006: 24.3; *grep* fails to display line numbers with global-linum-mode Mark Lillibridge
2013-12-06 17:50 ` Stefan Monnier
2013-12-10 21:27 ` Mark Lillibridge
2020-08-12 22:34 ` Stefan Kangas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmk8P0r0XDoVurLFQimLETxfNVe1J5O8t5=gLBF2N_M3GQ@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=16006-done@debbugs.gnu.org \
--cc=mdl@alum.mit.edu \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.