Re: master d506d91b1f 2/2: Make linum.el obsolete

[Philip Kaludercic]

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.