From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#56796: 29.0.50; Hard newlines not respected in code comments? Date: Fri, 29 Jul 2022 11:47:09 -0400 Message-ID: References: <8735ema73q.fsf@gmail.com> <83k07xaea1.fsf@gnu.org> <87fsikynn1.fsf@gmail.com> Reply-To: Stefan Monnier Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12438"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: 56796@debbugs.gnu.org, eliz@gnu.org To: Visuwesh Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 29 17:48:13 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 1oHSDk-00033E-Ji for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 29 Jul 2022 17:48:12 +0200 Original-Received: from localhost ([::1]:53592 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oHSDj-00060u-CS for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 29 Jul 2022 11:48:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51150) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oHSDa-00060l-Gn for bug-gnu-emacs@gnu.org; Fri, 29 Jul 2022 11:48:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:43544) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oHSDa-0007au-7X for bug-gnu-emacs@gnu.org; Fri, 29 Jul 2022 11:48:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oHSDa-0001uv-32 for bug-gnu-emacs@gnu.org; Fri, 29 Jul 2022 11:48:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Monnier Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 29 Jul 2022 15:48:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56796 X-GNU-PR-Package: emacs X-Debbugs-Original-Cc: "Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors" , Eli Zaretskii , 56796@debbugs.gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.16591096417201 (code B ref -1); Fri, 29 Jul 2022 15:48:02 +0000 Original-Received: (at submit) by debbugs.gnu.org; 29 Jul 2022 15:47:21 +0000 Original-Received: from localhost ([127.0.0.1]:33291 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHSCv-0001s5-1L for submit@debbugs.gnu.org; Fri, 29 Jul 2022 11:47:21 -0400 Original-Received: from lists.gnu.org ([209.51.188.17]:40844) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHSCs-0001ro-1X for submit@debbugs.gnu.org; Fri, 29 Jul 2022 11:47:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51024) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oHSCr-0005oe-Rd for bug-gnu-emacs@gnu.org; Fri, 29 Jul 2022 11:47:17 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:18383) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oHSCp-0007RX-OH; Fri, 29 Jul 2022 11:47:17 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 4383A100189; Fri, 29 Jul 2022 11:47:14 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id EB7A0100102; Fri, 29 Jul 2022 11:47:12 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1659109632; bh=xjAtfMAleQym8lgqMxNCEw1OmqHTPAyiZXv3SnTcitI=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=pZkFvmn94OjdxnR1C75RflTLslTUPZTDdpXY4bLvuGm1WFrhUcgODaZLG9wBJolF2 RDsPR1dz2b5VkL5dUXE4a6uHWdo/0RdaS1XFE8VLJ6QoLVxK9Wcvdb7z8GtMrkYoIC D4plDLutV7MKM1euQ2YPQxxesF/HyGMAgcArhshuZG8Y/bJqbEGDBnn2r8VkAOsVLQ VE5XPmHBLgySw5U2t5Kcp7ZqY2S4aTlUgKPICdPTETIUSvOj9adtlYjKLNKiVhAgk7 pdnEWwDoSojXFRr1/Vg9wFiik3OgWQFyXFWUvOsHujMVVtoh6dFHNmJAgeceVrxV6b 9JeZTzmZfWkkQ== Original-Received: from milanesa (dyn.144-85-172-183.dsl.vtx.ch [144.85.172.183]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 123E51203F3; Fri, 29 Jul 2022 11:47:11 -0400 (EDT) In-Reply-To: <87fsikynn1.fsf@gmail.com> (Visuwesh's message of "Fri, 29 Jul 2022 20:25:14 +0530") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:238195 Archived-At: > More generally: I'm not sure how common this pattern is but I tend to do > > ;; TODO/FIXME: Something... > ;; Ideas and thoughts on how to clear it here. > > Now if you do M-q there, your neatly arranged text is destroyed. (I am > probably biased) I also catch this pattern in the Emacs source tree as > well. It never occurred to me to use hard newlines for such cases. What I use instead is either: - add extra newlines to mark the paragraph boundaries to use (that's just as easy as adding hard newlines, but requires removing those extra newlines afterward). - Select the intended paragraph rather than rely on M-q's automatic decision of what's a paragraph. Hard newlines are a good idea, for this use-case, indeed, tho it would be even better if we could somehow represent that info in the text itself so it's properly saved into the file. Stefan