From: Stefan Kangas <stefankangas@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: master d506d91b1f 2/2: Make linum.el obsolete
Date: Wed, 21 Sep 2022 15:19:13 -0400 [thread overview]
Message-ID: <CADwFkmkTRJUf_igFcoxsudXGEp3O3Kg3g8gMjEt9j+_uTvG1NQ@mail.gmail.com> (raw)
In-Reply-To: <875yhgmvm4.fsf@posteo.net>
Philip Kaludercic <philipk@posteo.net> writes:
>> If we still have a feeling in 2032 that there are users out there, we
>> can always just postpone its removal for N more years. We've done that
>> before.
>
> What other examples are there?
See for example the comment in `interactive-p', or Bug#50999 on deleting
obsolete libraries in Emacs 29.1.
> I have the impression that line numbering is a pretty popular feature,
> that might be lingering around in many configurations for ages without
> anyone noticing it.
That concern is valid, however I do think our track record shows that we
can and do take such concerns into account when deciding whether or not
we should delete obsolete things.
next prev parent reply other threads:[~2022-09-21 19:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166370103866.17769.3203831255447980421@vcs2.savannah.gnu.org>
[not found] ` <20220920191039.C61BCC00874@vcs2.savannah.gnu.org>
2022-09-21 7:50 ` master d506d91b1f 2/2: Make linum.el obsolete Philip Kaludercic
2022-09-21 8:37 ` Stefan Kangas
2022-09-21 9:45 ` Philip Kaludercic
2022-09-21 12:35 ` Stefan Kangas
2022-09-21 12:43 ` Philip Kaludercic
2022-09-21 13:58 ` Stefan Kangas
2022-09-21 16:13 ` [External] : " Drew Adams
2022-09-21 16:36 ` Stefan Kangas
2022-09-21 18:26 ` Philip Kaludercic
2022-09-21 19:19 ` Stefan Kangas [this message]
2022-09-22 2:59 ` Po Lu
2022-09-22 11:01 ` Stefan Kangas
2022-09-22 11:50 ` Po Lu
2022-09-22 13:31 ` Stefan Monnier
2022-09-22 14:01 ` Stefan Kangas
2022-09-22 14:15 ` Stefan Monnier
2022-09-21 16:17 ` chad
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=CADwFkmkTRJUf_igFcoxsudXGEp3O3Kg3g8gMjEt9j+_uTvG1NQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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.