bug#58220: global-linum-mode emacs29

bug#58220: global-linum-mode emacs29

[Gwang-Jin Kim]

[-- Attachment #1: Type: text/plain, Size: 229 bytes --]

deactivating or removing `global-linum-mode` is a stupid idea, in my view.
One has to correct packages which are not workign any more emacs29.
Please add global-linum-mode back into emacs29 - for backwards
compatibility reasons.

[-- Attachment #2: Type: text/html, Size: 286 bytes --]

bug#58220: global-linum-mode emacs29

[Lars Ingebrigtsen]

Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com> writes:

> deactivating or removing `global-linum-mode` is a stupid idea, in my view.
> One has to correct packages which are not workign any more emacs29.
> Please add global-linum-mode back into emacs29 - for backwards compatibility
> reasons.

It's still in Emacs 29, and you can continue to use it as before.

(But it will be removed at some point, since there are many newer
solutions that work better.)

Closing.

bug#58220: global-linum-mode emacs29

[Colin Baxter]

>>>>> Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com> writes:

    > deactivating or removing `global-linum-mode` is a stupid idea, in
    > my view.  One has to correct packages which are not workign any
    > more emacs29.  Please add global-linum-mode back into emacs29 -
    > for backwards compatibility reasons.

I've put a copy of linum.el in my own lisp directory (together with
other soon-to-be or already-been obsoleted libraries). I then have
that directory sourced early in the load-path. That way I'll not be
affected when the axe finally falls.

Best wishes,

bug#58220: global-linum-mode emacs29

[Jean Louis]

* Lars Ingebrigtsen <larsi@gnus.org> [2022-10-01 15:19]:
> Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com> writes:
> 
> > deactivating or removing `global-linum-mode` is a stupid idea, in my view.
> > One has to correct packages which are not workign any more emacs29.
> > Please add global-linum-mode back into emacs29 - for backwards compatibility
> > reasons.
> 
> It's still in Emacs 29, and you can continue to use it as before.
> 
> (But it will be removed at some point, since there are many newer
> solutions that work better.)

I do not have that in development version.

Which other function should I use to get lines numbered?

--
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

bug#58220: global-linum-mode emacs29

[Stefan Kangas]

Jean Louis <bugs@gnu.support> writes:

> Which other function should I use to get lines numbered?

These are your options, in order of preference:

1. (global-display-line-numbers-mode 1)
2. (progn (package-install 'nlinum) (global-nlinum-mode 1))
3. (progn (require 'linum) (global-linum-mode 1))

Maybe we should add the above to NEWS?

bug#58220: global-linum-mode emacs29

[Lars Ingebrigtsen]

Stefan Kangas <stefankangas@gmail.com> writes:

> 1. (global-display-line-numbers-mode 1)
> 2. (progn (package-install 'nlinum) (global-nlinum-mode 1))
> 3. (progn (require 'linum) (global-linum-mode 1))
>
> Maybe we should add the above to NEWS?

Makes sense to me.

bug#58220: global-linum-mode emacs29

[Stefan Kangas]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> 1. (global-display-line-numbers-mode 1)
>> 2. (progn (package-install 'nlinum) (global-nlinum-mode 1))
>> 3. (progn (require 'linum) (global-linum-mode 1))
>>
>> Maybe we should add the above to NEWS?
>
> Makes sense to me.

Now done (commit 9cb3813550).  I didn't include instructions for how to
use 'linum', as it's better to just use 'nlinum' in that case.

bug#58220: global-linum-mode emacs29

[Eli Zaretskii]

> Cc: 58220@debbugs.gnu.org, Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com>
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Wed, 5 Oct 2022 15:51:44 -0700
> 
> Jean Louis <bugs@gnu.support> writes:
> 
> > Which other function should I use to get lines numbered?
> 
> These are your options, in order of preference:
> 
> 1. (global-display-line-numbers-mode 1)
> 2. (progn (package-install 'nlinum) (global-nlinum-mode 1))
> 3. (progn (require 'linum) (global-linum-mode 1))
> 
> Maybe we should add the above to NEWS?

It's a good idea, IMO.

bug#58220: global-linum-mode emacs29

[Eli Zaretskii]

> Cc: 58220@debbugs.gnu.org, Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com>,
>  Jean Louis <bugs@gnu.support>
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 6 Oct 2022 01:38:16 +0200
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > Stefan Kangas <stefankangas@gmail.com> writes:
> >
> >> 1. (global-display-line-numbers-mode 1)
> >> 2. (progn (package-install 'nlinum) (global-nlinum-mode 1))
> >> 3. (progn (require 'linum) (global-linum-mode 1))
> >>
> >> Maybe we should add the above to NEWS?
> >
> > Makes sense to me.
> 
> Now done (commit 9cb3813550).  I didn't include instructions for how to
> use 'linum', as it's better to just use 'nlinum' in that case.

I'd suggest to include linum as well.  We don't know the users'
preferences, and shouldn't second-guess them in this case.  The notes
about backward compatibilities in NEWS are supposed to help users who
want their old ways no matter what.  These notes do not provide our
preferences and recommendations, because those are apparent from the
defaults.

bug#58220: global-linum-mode emacs29

[Stefan Kangas]

Eli Zaretskii <eliz@gnu.org> writes:

> I'd suggest to include linum as well.  We don't know the users'
> preferences, and shouldn't second-guess them in this case.  The notes
> about backward compatibilities in NEWS are supposed to help users who
> want their old ways no matter what.  These notes do not provide our
> preferences and recommendations, because those are apparent from the
> defaults.

OK, that makes sense.  So I've added it (commit 039ada6d03).

If anyone wants to make any further adjustments or tweaks, please go
ahead.

bug#58220: global-linum-mode emacs29

[Jean Louis]

* Stefan Kangas <stefankangas@gmail.com> [2022-10-06 01:52]:
> Jean Louis <bugs@gnu.support> writes:
> 
> > Which other function should I use to get lines numbered?
> 
> These are your options, in order of preference:
> 
> 1. (global-display-line-numbers-mode 1)

Thank you.

It means M-x display-line-numbers-mode -- so it is just matter of a
habit, I was used to linum-mode

as why would I use it globally? Makes no sense to me.



-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

bug#58220: global-linum-mode emacs29

[Jean Louis]

* Stefan Kangas <stefankangas@gmail.com> [2022-10-06 10:12]:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > I'd suggest to include linum as well.  We don't know the users'
> > preferences, and shouldn't second-guess them in this case.  The notes
> > about backward compatibilities in NEWS are supposed to help users who
> > want their old ways no matter what.  These notes do not provide our
> > preferences and recommendations, because those are apparent from the
> > defaults.
> 
> OK, that makes sense.  So I've added it (commit 039ada6d03).
> 
> If anyone wants to make any further adjustments or tweaks, please go
> ahead.

In (info "(emacs) Acknowledgments") there is reference to:

   • Markus Triska wrote ‘linum.el’, a minor mode that displays line
     numbers in the left margin.

So if you are taking package out, consider that such reference may
confuse new users.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

bug#58220: global-linum-mode emacs29

[Eli Zaretskii]

> Date: Thu, 6 Oct 2022 10:50:18 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org,
>   58220-done@debbugs.gnu.org, gwang.jin.kim.phd@gmail.com
> 
> In (info "(emacs) Acknowledgments") there is reference to:
> 
>    • Markus Triska wrote ‘linum.el’, a minor mode that displays line
>      numbers in the left margin.
> 
> So if you are taking package out, consider that such reference may
> confuse new users.

Sorry, no.  We won't rewrite the history.  (And I don't think new
users will hurry up to read that section anyway.)