From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#64535: 30.0.50; Spurious newlines in `prin1` output Date: Thu, 10 Aug 2023 16:00:39 +0000 Message-ID: <3283828c97f247a07062@heytings.org> References: <83v8etbrhe.fsf@gnu.org> <83cz0ufwan.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22417"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 64535@debbugs.gnu.org, Eli Zaretskii To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 10 18:02:27 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 1qU87H-0005an-66 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 10 Aug 2023 18:02:27 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qU866-0001RY-ES; Thu, 10 Aug 2023 12:01:14 -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 1qU85v-0001LI-0Z for bug-gnu-emacs@gnu.org; Thu, 10 Aug 2023 12:01:03 -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 1qU85u-00089y-PB for bug-gnu-emacs@gnu.org; Thu, 10 Aug 2023 12:01:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qU85u-0000UY-3Q for bug-gnu-emacs@gnu.org; Thu, 10 Aug 2023 12:01:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 10 Aug 2023 16:01:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64535 X-GNU-PR-Package: emacs Original-Received: via spool by 64535-submit@debbugs.gnu.org id=B64535.16916832431849 (code B ref 64535); Thu, 10 Aug 2023 16:01:02 +0000 Original-Received: (at 64535) by debbugs.gnu.org; 10 Aug 2023 16:00:43 +0000 Original-Received: from localhost ([127.0.0.1]:43891 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qU85b-0000Tl-0v for submit@debbugs.gnu.org; Thu, 10 Aug 2023 12:00:43 -0400 Original-Received: from heytings.org ([95.142.160.155]:32776) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qU85Z-0000Tc-5F for 64535@debbugs.gnu.org; Thu, 10 Aug 2023 12:00:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1691683240; bh=NmP4R0IKWO1fukgkwHmsb04y+4DAItOC2IrF/6oQcEA=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=7N5LvOgbZ32vemeYCyi0VxST8pk8XZ1lw+Z3jTuGl7cw5ha8ui3mSQFHOzslYMTxU 7ySjzHvK/qa+WqILT+RHWNUR1eEAd65unt/E4yHIGusud63g/sgbkC5j5BW/iVmNQV tVkZO1nNrmZ0FISdxVE2QiAReGpV5Ng4kIX+gWe3udYwTiorl+I0RF2OpBm09fWFkW l/nP/y+gLa1XqmmRnM5/i8AoXUMJsh2vUjfKI7nkiHQYTo1yUPZAz97japtjFMPSDE y909w433uj0V32Q4ZHFAbgBvD/lARYtvtyV8sKdNf/RrhDO+HehXKMndGd71PUPz1r l74/UV1T8onsA== In-Reply-To: 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:267145 Archived-At: > > We now have a general way to solve the problem. I don't think it's > always absolutely perfect, but it's definitely good enough that we can > get rid of this odd hack. And those user who set `long-line-threshold` > to nil *and* happen to reproduce just the recipe in Bug#2866 would get > what they ask for, IMO. > FWIW, I agree with Stefan here. long-line-threshold is a fire escape, and users are advised to not change its value: "There is no reason to change that value except for debugging purposes." So his proposed fix, which removes a workaround installed by Mattias in May 2022, is safe.