From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Visuwesh Newsgroups: gmane.emacs.bugs Subject: bug#56796: 29.0.50; Hard newlines not respected in code comments? Date: Thu, 28 Jul 2022 13:50:06 +0530 Message-ID: <87pmhpodhl.fsf@gmail.com> References: <8735ema73q.fsf@gmail.com> <83k07xaea1.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="32623"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Stefan Monnier , 56796@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jul 28 10:32:24 2022 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 1oGywR-0008OK-Qn for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 28 Jul 2022 10:32:23 +0200 Original-Received: from localhost ([::1]:44386 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oGywQ-0001a0-Ir for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 28 Jul 2022 04:32:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48944) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oGylT-0003iT-8R for bug-gnu-emacs@gnu.org; Thu, 28 Jul 2022 04:21:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39547) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oGylT-0002gj-05 for bug-gnu-emacs@gnu.org; Thu, 28 Jul 2022 04:21:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oGylS-0004md-KY for bug-gnu-emacs@gnu.org; Thu, 28 Jul 2022 04:21:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Visuwesh Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 28 Jul 2022 08:21:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56796 X-GNU-PR-Package: emacs Original-Received: via spool by 56796-submit@debbugs.gnu.org id=B56796.165899643418321 (code B ref 56796); Thu, 28 Jul 2022 08:21:02 +0000 Original-Received: (at 56796) by debbugs.gnu.org; 28 Jul 2022 08:20:34 +0000 Original-Received: from localhost ([127.0.0.1]:57529 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oGykz-0004lP-V5 for submit@debbugs.gnu.org; Thu, 28 Jul 2022 04:20:34 -0400 Original-Received: from mail-pl1-f193.google.com ([209.85.214.193]:38424) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oGykw-0004l5-Uh for 56796@debbugs.gnu.org; Thu, 28 Jul 2022 04:20:31 -0400 Original-Received: by mail-pl1-f193.google.com with SMTP id o3so1179339ple.5 for <56796@debbugs.gnu.org>; Thu, 28 Jul 2022 01:20:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :user-agent:mime-version:content-transfer-encoding; bh=VXAnLY23gKc7p5k/aUCYclmu5772DGQokS2gTOhCnG0=; b=VHtlNOpHLuLMKDTEpFfqHFmMffK7taGq3i6psq9kNd1Ro9SpsDYH4Tipa5pROjO5Yp kZgDdEcbOMLTU5T1aJw/5iSh/fiXqeHf3JH1IAs9Seoc7HxxQ/kpas9H4GlbhUKqN7pn HMICKOm6Cx62rbYgDEXSySq+uHu2Cg7ehPu87iQEM4xIC9COD76MB2H6u+97IagNMmIq oZ+ayKr4JuGKYZicwl/Jr1K1lWuTOzwrXtJVX+dNkjL+gciXNINR5eNqIDFldzfVVv46 DtQHYPYtXLHTeGH9lfcbuNujRnL2AF6Vwn5u9ucSGlGcuXBhRCaDchdfBEqWktUdkKVB 23lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:user-agent:mime-version:content-transfer-encoding; bh=VXAnLY23gKc7p5k/aUCYclmu5772DGQokS2gTOhCnG0=; b=x2y6IbKGjXDRPek7XCqN6b/6kB3Q9kQmraMeTkdCG9I87IZCWLuX2wWsAKOVeGyVjF jNHLOUCgB4sWol72V1tfRKRe+vRgLgpiEYxF0Q77el5FUwwVBoqqC8M8XSNr1Nx0nmyY OSMAjuxAAlgrbbK/JW+kAlTG9XoxKFUT/36KbljaliSST9HgjWTmCMxuHLHK37FUFPRY V1PC1hGx0WQyNTZkwk152hcnylDzU+6ggeXj7R2SzlQFXk4i9uE12tmnA55LAba0Okjh EsMGr8UkELs5RUYfsZrAOpWgUX35I6z7MelvvuBz4dBBoKXGgGD2M6TtQh1qCWCgbd79 ya0g== X-Gm-Message-State: AJIora9u+pi3P8anVAtE3C9qAypeRHQK6lef6LVp5vjReo6Fmp5yTKTT Px884T9GJ9O0YmtQVcfKFbo= X-Google-Smtp-Source: AGRyM1uWXPq9phLXoo99PXFtSA2RAtn4wlikCwUGm5iTSR6f0tRcf0DY0ehBqhhCSi+SGaxbC6ZKzQ== X-Received: by 2002:a17:903:245:b0:16b:9c49:6b1c with SMTP id j5-20020a170903024500b0016b9c496b1cmr24480183plh.153.1658996424795; Thu, 28 Jul 2022 01:20:24 -0700 (PDT) Original-Received: from localhost ([49.204.141.236]) by smtp.gmail.com with ESMTPSA id f4-20020a62db04000000b005251fc16ff8sm3497pfg.220.2022.07.28.01.20.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Jul 2022 01:20:24 -0700 (PDT) In-Reply-To: <83k07xaea1.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 28 Jul 2022 10:26:46 +0300") 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" Xref: news.gmane.io gmane.emacs.bugs:238080 Archived-At: [=E0=AE=B5=E0=AE=BF=E0=AE=AF=E0=AE=BE=E0=AE=B4=E0=AE=A9=E0=AF=8D =E0=AE=9C= =E0=AF=82=E0=AE=B2=E0=AF=88 28, 2022] Eli Zaretskii wrote: >> From: Visuwesh >> Date: Wed, 27 Jul 2022 21:19:29 +0530 >>=20 >> Are hard newlines supposed to be respected when they are in code >> comments? > > The answer is "it depends", AFAICS. > > The main problem is that fill-comment-paragraph doesn't seem to honor > use-hard-newlines. So any major mode whose fill-paragraph-function > uses that for filling comments will fail to pay attention to hard > newlines in comments. In your scenario, if I set both > fill-paragraph-function and fill-paragraph-handle-comment to nil, hard > newlines in comments are honored as expected. Thanks for the explanation, I figured that was the case. > If we want use-hard-newlines to be supported in comments, we should > modify fill-comment-paragraph to honor it in some way, perhaps simply > deferring to fill-region in that case. That would be most welcome. Hard newlines was the "missing key" in making writing plain text more easy and enjoyable to me.