From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: larsi@gnus.org, bugs@gnu.support, 58220@debbugs.gnu.org,
gwang.jin.kim.phd@gmail.com
Subject: bug#58220: global-linum-mode emacs29
Date: Thu, 06 Oct 2022 09:08:32 +0300 [thread overview]
Message-ID: <83wn9dqyan.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkfmCdvtnOQ33=kb8hSgvsa5SH7+EwMjSZ+Hv9nOipkaw@mail.gmail.com> (message from Stefan Kangas on Thu, 6 Oct 2022 01:38:16 +0200)
> 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.
next prev parent reply other threads:[~2022-10-06 6:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 11:15 bug#58220: global-linum-mode emacs29 Gwang-Jin Kim
2022-10-01 12:17 ` Lars Ingebrigtsen
2022-10-05 18:51 ` Jean Louis
2022-10-05 22:51 ` Stefan Kangas
2022-10-05 23:12 ` Lars Ingebrigtsen
2022-10-05 23:38 ` Stefan Kangas
2022-10-06 6:08 ` Eli Zaretskii [this message]
2022-10-06 7:11 ` Stefan Kangas
2022-10-06 7:50 ` Jean Louis
2022-10-06 8:14 ` Eli Zaretskii
2022-10-06 6:03 ` Eli Zaretskii
2022-10-06 7:48 ` Jean Louis
2022-10-01 13:08 ` Colin Baxter
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=83wn9dqyan.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58220@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=gwang.jin.kim.phd@gmail.com \
--cc=larsi@gnus.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).