From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id oGndLB3XKWMHSwEAbAwnHQ (envelope-from ) for ; Tue, 20 Sep 2022 17:07:09 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id sHnMLB3XKWMgGgEAauVa8A (envelope-from ) for ; Tue, 20 Sep 2022 17:07:09 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B684B100E0 for ; Tue, 20 Sep 2022 17:06:42 +0200 (CEST) Received: from localhost ([::1]:44512 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oaepd-0002FJ-T1 for larch@yhetil.org; Tue, 20 Sep 2022 11:06:41 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56622) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oacXm-00089Z-1m for emacs-orgmode@gnu.org; Tue, 20 Sep 2022 08:40:07 -0400 Received: from mail-pl1-x641.google.com ([2607:f8b0:4864:20::641]:40528) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oacXj-0003PU-Po for emacs-orgmode@gnu.org; Tue, 20 Sep 2022 08:40:05 -0400 Received: by mail-pl1-x641.google.com with SMTP id b21so2223377plz.7 for ; Tue, 20 Sep 2022 05:40:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date; bh=cWOzAWVyK45oiuh1udY4PgBa9Ntg2Qhz4zvwmcdQhpA=; b=SMyS6O9dRK1LzGNaYsj2bG2hhihrQ2Puz7UxD9oIIheOCsapM3++1pwyk7N8REjVXP TlI61DMKBI55D9Av58d3qU5FOnWkirg3d1Z5eglgcPT+4tWxCJXaXLM29kfFrjhROpg8 BbkcSKI8geQJcbrVr7MqrmygIy6hz6BDGLXFm3LxX/R22VxI9yz1Y7duYnrlT89zbFMo jLxog+ju6rlkvlVaRuphbZuK8jQ3UUpOsmejR+6CIv6WIfhwMwpLfHp3X/GI8WMeCP+9 scNxtsldDEiuenvXXkRYvNRxcNsXpBplWImt0QtOfpNMxiCHsv+6rVIyekjegkjBB8Zx UGiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date; bh=cWOzAWVyK45oiuh1udY4PgBa9Ntg2Qhz4zvwmcdQhpA=; b=1/kAnKSTeMFSqm0L74OXAYfrPT6T2UXstHRsMe6HUWi1Ekl9xOfIlIqHSM4ATMAeRj gTxvG6NGulkAhHN0eIhjyyeDh0WTQT2TfWxQMAShGg8S7v0Q1+oD5KxM/Tg1N6IWvatG 3N7osaHBz7oAHeGi5yruw7Lwl88tzkNoX+7yeO/fV9WGdoCgp7ZdWc2lP2IIckdyp7WF iGaLTUOaXE0QSvuy5UbLgfJ1SUzoembKHX4V55yFsZ2D2MFGe1Ihrgh/jR47arFT+Z6x urXtby0x3K26NYXUE5qeidGDGkIB8N6EMBe5GLWlXgqkc8gsrwJHOxCvba7W4uJjk6Cs OhYg== X-Gm-Message-State: ACrzQf2xq41TUxMHvJRo/9qoxpOzFLiqY96/WIxtU84M+aj5bkKwyGIh jOJnIZky2MtxtquC1tJg8Js= X-Google-Smtp-Source: AMsMyM5UDU0tQCaPyctmihfomo/ELvWM9b71S6LjM+YS6Wpx48kpE31aG3CLYgyLkPShqLgDBSxEYg== X-Received: by 2002:a17:90b:1801:b0:202:7cf6:9f93 with SMTP id lw1-20020a17090b180100b002027cf69f93mr3672355pjb.170.1663677600611; Tue, 20 Sep 2022 05:40:00 -0700 (PDT) Received: from localhost ([14.139.216.98]) by smtp.gmail.com with ESMTPSA id p4-20020a170902780400b001782aab6318sm1320199pll.68.2022.09.20.05.39.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 20 Sep 2022 05:39:59 -0700 (PDT) From: Visuwesh To: Ihor Radchenko Cc: emacs-orgmode@gnu.org Subject: Re: FR: support hard-newlines [9.5.5 (release_9.5.5 @ /home/viz/lib/ports/emacs/lisp/org/)] In-Reply-To: <87mtauz1f6.fsf@localhost> (Ihor Radchenko's message of "Tue, 20 Sep 2022 20:16:13 +0800") References: <87pmftqkf1.fsf@gmail.com> <87mtauz1f6.fsf@localhost> Date: Tue, 20 Sep 2022 18:09:57 +0530 Message-ID: <87pmfqmd7m.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::641; envelope-from=visuweshm@gmail.com; helo=mail-pl1-x641.google.com 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-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1663686402; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=cWOzAWVyK45oiuh1udY4PgBa9Ntg2Qhz4zvwmcdQhpA=; b=GJG/KVjloaQ0avaGMJdhxt274tNKgWGoxlIYRAVcg5Vkhc2HmgnlyoNmsy7d8jCppJJajL 1OHYFizlN6UMGc0HwcMY5XGzyPRkXULahYeItDiYG45QKkZBZ+COewYtcqAe6R4YxzbLkg M1PocjOJOq2ip9QF5JTRxLxxjw8znNwWEfqguCs/VYv2bOlyNRFetBP25yOrDFJtE/ICrh TLOi6od/KTinGiu82i+IhTQX2oNYKQ0SI+XGtvTyvhjMIy0324+RWyK0TzoPDW2isr7myV D7s5JM4qywwkZeuEKizHiTVVpi17aY/lW82qk4DrV9hYP3s2mrgN5GNv7TofRw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1663686402; a=rsa-sha256; cv=none; b=ZS+V4tHPS5BUuVw5qgMjIxTVlqqaH7SI0cQdNuzXFF07uGOXCJt11dgwLrUohYOzj4bXTE PGs7baALVMRr7wVlzsNKi7LKvj537RG46KSKyzymWjQVtOSe+U2EUA9pXXEKxJhLVWYfRD 5pfWYA8KhBdzZ/SziD4+hX8rxOZII+HveYFe19rjxqjED8F+Oms3J/YuZc25CVSUUhmqet sF69TtnapA49OYK6Z9d18olWMbhlJRfJK4SRydVfTmMkHLHcsaHJAX9KUKuNiQwXMCj96T oOZv3RfpNYdm8T++dQGvemIAveMMZbspZXaB7PXxhaRifESCUezzzV2L/967Gg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=SMyS6O9d; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -2.33 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b=SMyS6O9d; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: B684B100E0 X-Spam-Score: -2.33 X-Migadu-Scanner: scn1.migadu.com X-TUID: dCSEecAqystV [=E0=AE=9A=E0=AF=86=E0=AE=B5=E0=AF=8D=E0=AE=B5=E0=AE=BE=E0=AE=AF=E0=AF=8D = =E0=AE=9A=E0=AF=86=E0=AE=AA=E0=AF=8D=E0=AE=9F=E0=AE=AE=E0=AF=8D=E0=AE=AA=E0= =AE=B0=E0=AF=8D 20, 2022] Ihor Radchenko wrote: >> 1. When you want to end a line with a link and continue text in the >> next line. You don't care about the export since it will be >> taken care of properly. >> 2. When reflowing text with inline latex in them. You adjust the >> line width so that it looks like 80 columns are present in a >> single line. With hard-newlines, this becomes a very easy job >> without with you have to isolate the line of interest into a >> separate paragraph, then do the manual reflow, rinse and repeat. > > This sounds as a reasonable use case. However, the Emacs definition of > hard newlines also involves re-defining paragraph breaks. I do not think > that it is a good idea for Org to alter Org paragraph syntax depending > on `use-hard-newlines' - it will create too much confusion when Org > documents are opened outside Emacs. I do not think it is necessary for org to recognise hard-newlines as a paragraph break either since, after all, the presence of hard-newlines is ephemeral. >> 3. When writing a list, you give a short description at the top. >> Then continue writing down below like this without the need to >> insert a empty line after the first line. > > Note that _not_ having an empty line after the first line can be > misleading. In Org syntax, absence of line will merge description and > the text below into a single paragraph. It will, for example, affect > export. I do get your point, but sometimes there are situations where merging does not cause confusion and I would like to have the ability to write lists like no. 3. This is more true when you, like me, treat org-mode as a major-mode which enhances plain text files. If i was exporting, then I wouldn't rely on org-mode handling hard-newlines (kind of like how HTML behaves wrt requiring
). >> My point is that there are several instances where you need a solution >> that is less aggressive than \\ and hard-newlines hit that sweet spot >> perfectly. > > All in all, I feel that fully respecting `use-hard-newlines' in Org is > not a good idea. We can do it partially (for filling), but I am afraid > that it may create some confusion. I am not sure what you mean by confusion here: those who have `use-hard-newlines' turned on are explicitly asking for it. If anything, I was confused when I found org-mode did not recognise hard-newlines. >> - (fill-region-as-paragraph c end justify) >> + (fill-region c end justify) > > There are 3 calls to `fill-region-as-paragraph' inside > `org-fill-element'. If we decide to support `use-hard-newlines' > partially, all 3 calls should probably be replaced. AFAICT, the rest two are comments (though I cannot tell the difference between "comment" and "comment-block"). I replaced the one in paragraph since that was where lack of hard-newlines support bit me.