From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#64596: 30.0.50; On FIXME: in src/buffer.c:1481 (force-mode-line-update) Date: Fri, 14 Jul 2023 22:05:11 +0300 Message-ID: <83ttu6e2l4.fsf@gnu.org> References: <877cr4nez9.fsf@localhost> <83lefj4okb.fsf@gnu.org> <83fs5r3tqv.fsf@gnu.org> <834jm6fppc.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39759"; mail-complaints-to="usenet@ciao.gmane.io" Cc: yantar92@posteo.net, 64596@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 14 21:05:19 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1qKO6Q-000A7R-W9 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 14 Jul 2023 21:05:19 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qKO6C-0007su-F8; Fri, 14 Jul 2023 15:05:04 -0400 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 1qKO6A-0007sO-TN for bug-gnu-emacs@gnu.org; Fri, 14 Jul 2023 15:05:02 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qKO6A-0003AJ-Ld for bug-gnu-emacs@gnu.org; Fri, 14 Jul 2023 15:05:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qKO6A-0002Ce-HF for bug-gnu-emacs@gnu.org; Fri, 14 Jul 2023 15:05:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 14 Jul 2023 19:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64596 X-GNU-PR-Package: emacs Original-Received: via spool by 64596-submit@debbugs.gnu.org id=B64596.16893615018451 (code B ref 64596); Fri, 14 Jul 2023 19:05:02 +0000 Original-Received: (at 64596) by debbugs.gnu.org; 14 Jul 2023 19:05:01 +0000 Original-Received: from localhost ([127.0.0.1]:43515 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qKO68-0002CE-NW for submit@debbugs.gnu.org; Fri, 14 Jul 2023 15:05:01 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:32806) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qKO67-0002C2-3r for 64596@debbugs.gnu.org; Fri, 14 Jul 2023 15:05:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qKO61-00035k-4H; Fri, 14 Jul 2023 15:04:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=8Zszn1UGc6S+eTIEknOfybrH6Dht3bes5ejmd3ZuMtI=; b=VWtbUFQQBBMn il8esAbNmRGmU3jb0uvfeY4FfJiR3YYxSP+U3eM1snyoFPzFesF3QV14lhOClzZU6BvLbErobohnm kzf7sT30/ysEPU2NByNv7vIf9G4CzPDmxhha1FjhNbqC/K/xMo5wGM1Fg4Np5+yHEi9Dqd7fMZbKL Liqdc11FablySMcW0m73iYH3xOz5LRkJ1zRB3tAesZEuLYgCyoCnNeoYlxnU68pUt49Asso1g++Nj 0/4pD+ZxzoMtbydN6kAUPbJIxIjqODlOjqWlupdMhJtuiWicl+TBzXsM/yo4Tc9ufmPgvU+g5U/Mw fEkZG9hIzGC8j41M1YER2w==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qKO60-0006tv-KP; Fri, 14 Jul 2023 15:04:52 -0400 In-Reply-To: (message from Stefan Monnier on Fri, 14 Jul 2023 13:38:11 -0400) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:265120 Archived-At: > From: Stefan Monnier > Cc: yantar92@posteo.net, 64596@debbugs.gnu.org > Date: Fri, 14 Jul 2023 13:38:11 -0400 > > > No, one variable is not enough -- it will never tell us which of the > > potential flags or settings of the flag requires to be reinstated. We > > need to be able to investigate this at a finer granularity. > > I doubt it. > > What we need in order to investigate is a somewhat reproducible test > case and for that we need the bug to be exposed to as many users as > possible to increase the chance that one of them bumps into > a good recipe. > > The variable is not used to investigate, but to make it ethical to > expose users to those potential bugs because they can set the var to > recover the old behavior as soon as they're tired of playing the > guinea pig. That's not what I had in mind when I proposed this approach. What I had in mind was to investigate the need for every one of the variables we use to disable redisplay optimizations in the various cases: the prevent_redisplay_optimizations_p flag, the update_mode_lines variable, the windows_or_buffers_changed variable, etc. -- in the places in xdisp.c where these are heeded. The purpose was to understand better which ones should be used where and why. This cannot be done with a single variable. So if you want a single variable for some "ethical" pseudo-investigation, I guess we deeply disagree here. I'm not interested in such "investigation".