unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: 57412@debbugs.gnu.org
Cc: stefan@marxist.se, monnier@iro.umontreal.ca, dgutov@yandex.ru
Subject: bug#57412: Could we make linum.el obsolete?
Date: Fri, 26 Aug 2022 21:17:47 +0100	[thread overview]
Message-ID: <87tu5ywyhg.fsf@yandex.com> (raw)
In-Reply-To: <jwv5yie256h.fsf-monnier+emacs@gnu.org> (Stefan Monnier via's message of "Fri, 26 Aug 2022 15:14:40 -0400")

>>>>> Bug reports for GNU Emacs, the Swiss army knife of text editors <Stefan> writes:

    > Colin Baxter [2022-08-26 20:00:40] wrote:
    >> 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.

    > Those that are useful but suffer from corner-case problems due to
    > the underlying design are bound to fall into this trap: if they
    > weren't very useful, noone would bother to reimplement them to fix
    > those corner cases but since the problems stem from the underlying
    > approach, the fix requires a significant rewrite which inevitably
    > leads to a slightly different featureset.

    > The purpose of obsoleting a library like `nlinum.el` is to
    > help/encourage people to move to the better options out there (and
    > sometimes also to discover important use-cases not yet covered by
    > the new code).

    > The maintenance cost of `nlinum.el` isn't very high, but there's a
    > cost for users of having to choose between various options, none
    > of which is a strict superset of the other.

I am not convinced. However thank you nevertheless for taking the time
and effort to explain.

Best wishes,





  reply	other threads:[~2022-08-26 20:17 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 [this message]
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=87tu5ywyhg.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=57412@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=monnier@iro.umontreal.ca \
    --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).