all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 58220@debbugs.gnu.org, Gwang-Jin Kim <gwang.jin.kim.phd@gmail.com>
Subject: bug#58220: global-linum-mode emacs29
Date: Wed, 5 Oct 2022 21:51:18 +0300	[thread overview]
Message-ID: <Yz3SJkZH0J6+tPaf@protected.localdomain> (raw)
In-Reply-To: <87tu4nhh5p.fsf@gnus.org>

* 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/





  reply	other threads:[~2022-10-05 18:51 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yz3SJkZH0J6+tPaf@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=58220@debbugs.gnu.org \
    --cc=gwang.jin.kim.phd@gmail.com \
    --cc=larsi@gnus.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.