unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Dmitry Gutov <dgutov@yandex.ru>
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 20:00:40 +0100	[thread overview]
Message-ID: <87sflieso7.fsf@yandex.com> (raw)
In-Reply-To: <4cc5c07f-75d4-3bc6-e3ff-bcf84c1ce261@yandex.ru> (Dmitry Gutov's message of "Fri, 26 Aug 2022 13:49:55 +0300")

>>>>> Dmitry Gutov <dgutov@yandex.ru> writes:

    > On 26.08.2022 11:20, Colin Baxter wrote:
    >>>>>>> Stefan Kangas<stefankangas@gmail.com> writes:
    >> > Severity: wishlist Is there any reason to keep linum.el around
    >> any > longer, or could it be marked obsolete in favor of >
    >> `display-line-numbers-mode'?  > Given our obsoletion policy, it
    >> would still be around for another > decade, which should give
    >> users plenty of time to adapt.  Please do not obsolete this. I do
    >> not like display-line-numbers-mode, preferring line numbers in
    >> the margin. There must be other users similarly inclined.

    > Have you tried nlinum-mode from GNU ELPA? I hear it has better
    > performance and apparently fewer bugs.

    >> I do not understand this need to obsolete packages that perform
    >> perfectly well. Emacs often has multiple ways of achieving the
    >> same outcome, which is surely a positive.

    > It's good to reduce the volume of code we have to support over
    > time.

    > It would also help people land on a faster and better supported
    > alternative.

Yes, I understand that and agree. From my perspective, I am disappointed
that candidates for obsolescence seem to be chosen from libraries that
are useful and not from morse, zone and the like.

Best wishes,





  reply	other threads:[~2022-08-26 19:00 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 [this message]
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=87sflieso7.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=57412@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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).