From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Konstantin Kharlamov Newsgroups: gmane.emacs.devel Subject: Re: Emacs 31.0.50 (2f1052d9b0de) will line-number in some buffers which shouldn't show it, is there some changed in recent master branch related to display-line-number Date: Fri, 03 Jan 2025 18:23:15 +0300 Message-ID: References: <87h66gcuxk.fsf@gmail.com> <86wmfcgu9t.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33207"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Evolution 3.54.2 Cc: emacs-devel@gnu.org To: Eli Zaretskii , Eval EXEC Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 03 16:23:51 2025 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tTjWh-0008Ut-J7 for ged-emacs-devel@m.gmane-mx.org; Fri, 03 Jan 2025 16:23:51 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tTjWM-00054L-Q0; Fri, 03 Jan 2025 10:23:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tTjWK-00053t-Nz for emacs-devel@gnu.org; Fri, 03 Jan 2025 10:23:28 -0500 Original-Received: from forward501b.mail.yandex.net ([2a02:6b8:c02:900:1:45:d181:d501]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tTjWH-0001SV-Dc; Fri, 03 Jan 2025 10:23:28 -0500 Original-Received: from mail-nwsmtp-smtp-production-main-44.sas.yp-c.yandex.net (mail-nwsmtp-smtp-production-main-44.sas.yp-c.yandex.net [IPv6:2a02:6b8:c08:df8e:0:640:17d3:0]) by forward501b.mail.yandex.net (Yandex) with ESMTPS id C6FCE60CD4; Fri, 3 Jan 2025 18:23:16 +0300 (MSK) Original-Received: by mail-nwsmtp-smtp-production-main-44.sas.yp-c.yandex.net (smtp/Yandex) with ESMTPSA id FNjg8tDOkSw0-H9z8QUl1; Fri, 03 Jan 2025 18:23:16 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1735917796; bh=w3xhLsiugoIyYc51tYI3GA+PUpIk5ir+JCKjd+i3yPs=; h=References:Date:In-Reply-To:Cc:To:From:Subject:Message-ID; b=R5WdUJN/7+D1TbBKijtDfSw6irxplqCDfwq0Q1uNhmt3c9yoNrmRpzgpMsYEW+kxl dv4uZnmQitd5GWqkkVVrlICCtTmpxjh1eFV0MaX9XUWCmdQZBKVPm7TrADStVH26QE /XI7PpSwEqmA8D2Rqd3wD0ftySFWmr7Swc2eGSUM= Authentication-Results: mail-nwsmtp-smtp-production-main-44.sas.yp-c.yandex.net; dkim=pass header.i=@yandex.ru In-Reply-To: <86wmfcgu9t.fsf@gnu.org> Received-SPF: pass client-ip=2a02:6b8:c02:900:1:45:d181:d501; envelope-from=Hi-Angel@yandex.ru; helo=forward501b.mail.yandex.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327630 Archived-At: On Fri, 2025-01-03 at 10:45 +0200, Eli Zaretskii wrote: > > From: Eval EXEC > > Date: Fri, 03 Jan 2025 13:45:11 +0800 > >=20 > >=20 > > --=20 > >=20 > >=20 > > Hello, I am building Emacs from source, and I=E2=80=99ve noticed someth= ing > > unusual. Line numbers appear in my rg and xref buffers, but they > > disappear after approximately 100ms. This happens even though I=E2=80= =99ve > > only > > configured display-line-number-mode to be enabled in prog-mode via > > an > > add-hook. >=20 > Can you show a minimal recipe for reproducing this problem starting > from "emacs -Q"? >=20 > It is best to post that using "M-x report-emacs-bug", so that this > and > the following discussion get recorded by our issue tracker. I join the Eli's comment: I just built Emacs and I can't reproduce your problem. Please try reducing it to minimal steps. Even better would be if you'd find the commit that brought the problem (see git-bisect, it's somewhat fast, e.g. for 2000 commits you can find the culprit in just 11 steps).