From: Jean Louis <bugs@gnu.support>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: gwang.jin.kim.phd@gmail.com, Eli Zaretskii <eliz@gnu.org>,
larsi@gnus.org, 58220-done@debbugs.gnu.org
Subject: bug#58220: global-linum-mode emacs29
Date: Thu, 6 Oct 2022 10:50:18 +0300 [thread overview]
Message-ID: <Yz6IuuUCv6pwBIWK@protected.localdomain> (raw)
In-Reply-To: <CADwFkmkaON0rSUKc2-JAMNkirTAfCPyfRJig9DHtunPhuzNdHA@mail.gmail.com>
* 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/
next prev parent reply other threads:[~2022-10-06 7:50 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
2022-10-06 7:11 ` Stefan Kangas
2022-10-06 7:50 ` Jean Louis [this message]
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=Yz6IuuUCv6pwBIWK@protected.localdomain \
--to=bugs@gnu.support \
--cc=58220-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).