unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: 57412@debbugs.gnu.org
Cc: monnier@iro.umontreal.ca
Subject: bug#57412: Could we make linum.el obsolete?
Date: Tue, 20 Sep 2022 15:10:48 -0400	[thread overview]
Message-ID: <CADwFkm=TAJ0uMKtpmU=ecLMLWghH78G183VwEfGjaJku2oX=Bg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmktLD5qk3KnoiPtF9vpBoGW86Qv0eeN7vXKpz8KPU+T5Q@mail.gmail.com> (Stefan Kangas's message of "Thu, 25 Aug 2022 18:08:06 +0000")

close 57412 29.1
thanks

Stefan Kangas <stefankangas@gmail.com> writes:

> Is there any reason to keep linum.el around any longer, or could it be
> marked obsolete in favor of `display-line-numbers-mode'?

(That was 4 weeks ago.)

Despite one notable objection on the grounds that it is still useful,
most people here seem to agree that we can go ahead and obsolete it,
given that it can be replaced by `nlinum' (on GNU ELPA) which is faster
and has less bugs.[1]

Meanwhile, Stefan Monnier pointed out that:[2]

> [O]bsoleting `linum.el` doesn't mean removing it from Emacs for
> several more years.  And even if/when we do decide to remove it, we
> can move it to GNU ELPA instead if there's still interest.

So I've now obsoleted linum.el in commit 903de63c6c and d506d91b1f, and
I'm closing this bug.  We recommend `nlinum' as a close to drop-in
replacement, alternatively `display-line-numbers-mode'.

Footnotes:
[1] Users also seem to like `nlinum', see e.g.:
     https://github.com/company-mode/company-mode/issues/1336

[2] Hopefully, however, Emacs will be shipping with nlinum.el included
     in our release tarballs by then.  We just need to figure out how to
     properly integrate GNU ELPA packages first.





      parent reply	other threads:[~2022-09-20 19:10 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
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 [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='CADwFkm=TAJ0uMKtpmU=ecLMLWghH78G183VwEfGjaJku2oX=Bg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=57412@debbugs.gnu.org \
    --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 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).