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 09:45:42 +0000 [thread overview]
Message-ID: <87v8phnjqx.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmny0kpK8E9O=EaEa1_LFTKvyfru7f4fErz-4KaKZiowrQ@mail.gmail.com> (Stefan Kangas's message of "Wed, 21 Sep 2022 01:37:39 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> If I try to load linum now, I just get a message that it is deprecated,
>
> That's weird, shouldn't that be
>
> diff --git a/lisp/subr.el b/lisp/subr.el
> index 59f9308f31..7a0896e91e 100644
> --- a/lisp/subr.el
> +++ b/lisp/subr.el
> @@ -5557,7 +5557,7 @@ do-after-load-evaluation
> (package (intern (substring file 0
> (string-match "\\.elc?\\>" file))
> obarray))
> - (msg (format "Package %s is deprecated" package))
> + (msg (format "Package %s is obsolete" package))
> (fun (lambda (msg) (message "%s" msg))))
> (when (or (not (fboundp 'byte-compile-warning-enabled-p))
> (byte-compile-warning-enabled-p 'obsolete package))
I'm not sure what you mean. Are we talking about the usage of
"deprecated" vs. "obsolete"?
>> but no hint to use `display-line-numbers-mode'. Can that be added?
>
> I don't think we have any way of displaying such messages. Maybe it
> would be worth adding, though.
Another idea might be to explicitly mark `linum-mode' as obsolete and
recommend using `display-line-numbers-mode' when it is enabled. Though
the issue here is probably that most people who use linum enable it on
startup and might miss the message.
next prev parent reply other threads:[~2022-09-21 9:45 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 [this message]
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
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=87v8phnjqx.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).