unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 57412@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
	monnier@iro.umontreal.ca
Subject: bug#57412: Could we make linum.el obsolete?
Date: Fri, 26 Aug 2022 14:19:59 +0300	[thread overview]
Message-ID: <001fc7b6-a724-b191-77a8-94c7eeec8a69@yandex.ru> (raw)
In-Reply-To: <87bks7dzu4.fsf@gnus.org>

On 26.08.2022 14:11, Lars Ingebrigtsen wrote:
> Eli Zaretskii<eliz@gnu.org>  writes:
> 
>> The only possible reason is that linum.el allows more freedom in
>> formatting the line numbers and their faces.  I don't know whether
>> this reason is serious enough to not obsolete linum.el.
> I think nlinum is supposed to support everything that linum does (and is
> faster and less buggy) -- but I haven't looked in detail.

Here's one such case when I ended just just recommending to avoid linum:

https://github.com/company-mode/company-mode/issues/1336





  reply	other threads:[~2022-08-26 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 18:08 bug#57412: Could we make linum.el obsolete? Stefan Kangas
2022-08-25 18:29 ` Eli Zaretskii
2022-08-26 11:11   ` Lars Ingebrigtsen
2022-08-26 11:19     ` Dmitry Gutov [this message]
2022-08-26 16:55       ` Colin Baxter
2022-08-26  8:20 ` Colin Baxter
2022-08-26 10:49   ` Dmitry Gutov
2022-08-26 19:00     ` Colin Baxter
2022-08-26 19:14       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 20:17         ` Colin Baxter
2022-08-26 21:11           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-26 16:18   ` Drew Adams
2022-09-20 19:10 ` Stefan Kangas

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=001fc7b6-a724-b191-77a8-94c7eeec8a69@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=57412@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=stefankangas@gmail.com \
    /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).