From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master d506d91b1f 2/2: Make linum.el obsolete
Date: Wed, 21 Sep 2022 12:43:48 +0000 [thread overview]
Message-ID: <87pmfonbi3.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmkObDUmmiCBcEmw1QVeomH3xtWP7ZYL4J_SXxa=-BnY5A@mail.gmail.com> (Stefan Kangas's message of "Wed, 21 Sep 2022 05:35:06 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> I'm not sure what you mean. Are we talking about the usage of
>> "deprecated" vs. "obsolete"?
>
> Yes, the directory is called "lisp/obsolete" after all.
I don't know if there are strict definitions, but to me these two are de
facto synonyms.
>> Another idea might be to explicitly mark `linum-mode' as obsolete and
>> recommend using `display-line-numbers-mode' when it is enabled.
>
> Yes, indeed. I've now made that change on master.
1+
>> Though the issue here is probably that most people who use linum
>> enable it on startup and might miss the message.
>
> True. Maybe we could think about ways to make the message more visible.
>
> We do have this comment in `do-after-load-evaluation':
>
> ;; Maybe we should just use display-warning? This seems yucky...
It is a tricky question. The question is will (most) people notice the
deprecation message before linum is removed from emacs.git/the release
that does so is distributed. I am guessing this could take a few years
to happen, then maybe 2-3 years until the release until whatever version
of Emacs that ends up being is even distributed by stable distribution
channels.
That might be long enough to notice a warning and fix it, or they will
start up Emacs one day after an update an encounter a void function
error.
Perhaps, when it comes to this, it might be enough to add a legacy alias
and make `linum-mode' invoke `display-line-numbers-mode', doing the same
for `global-linum-mode' and `global-display-line-numbers-mode'.
A more general idea might be to have some kind of init.el-health-checker
command that could detect and propose to fix simple issues like these.
But then again, will those who never pay attention notice this?
next prev parent reply other threads:[~2022-09-21 12:43 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 [this message]
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
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
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=87pmfonbi3.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--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).