From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.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 2HurKE7WMmMcAAEAbAwnHQ (envelope-from ) for ; Tue, 27 Sep 2022 12:54:06 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id aErZKE7WMmOrZQEA9RJhRA (envelope-from ) for ; Tue, 27 Sep 2022 12:54:06 +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 46CF12A38A for ; Tue, 27 Sep 2022 12:54:06 +0200 (CEST) Received: from localhost ([::1]:43334 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1od8E1-00046j-Ev for larch@yhetil.org; Tue, 27 Sep 2022 06:54:05 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:48652) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1od88R-0007ql-S9 for emacs-orgmode@gnu.org; Tue, 27 Sep 2022 06:48:19 -0400 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]:33659) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1od88P-0000qM-RQ for emacs-orgmode@gnu.org; Tue, 27 Sep 2022 06:48:19 -0400 Received: by mail-lf1-x12d.google.com with SMTP id d42so15175017lfv.0 for ; Tue, 27 Sep 2022 03:48:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:cc:references:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date; bh=B1l/QHNeM/hDwhhDsOS8ie6nPd0MWTH7mC64jiZWYco=; b=l2H+cgAhTdKSHPgCs86XgX3o2+SmYBKVodveN8sTtEtZAUmdVezbectLckBwc2sOJd jPKbJoL+gTdL1pUXP9EGGeB58/y9d/k6VtDdG/+GgUZB+PEiMiv64Pt6LTSNfPJNmxSR qq7Gv7va4WJ/S5hII6TO8vUoRqHCKicahhvWlRDh5o2zzGgmwqt1OY4YiiQy2oyaVwlM zEDgg9YbMvEhB2dTWm9v+UMAxsCFXnreLsuwWxh1gtVCv2+3cGDgU4favd9QFdKvg9k+ YJYb+1uQJSX0+IBLi78i/aKA8GhId10/RmNrnC/T2n/Xxj8Ny4ie+wEzD14914sHjaOs HHwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:cc:references:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date; bh=B1l/QHNeM/hDwhhDsOS8ie6nPd0MWTH7mC64jiZWYco=; b=q0W221KfME0NbPIznMXf4uo03FKutYKD3AY0myoJ4nKjj9ZfAq3gIsbUoe2eiv9y99 DjwKa5wSt01oFsMgB3E0olTHoNAQl3WYdsJhZoABn9yQsHb7nt+a+KUYDbxu4s1fTR5a hb0PKYEAg3ratIeISOO32x9flnCGkqBuk4jAhRNoE9xS/MrezM02w3ve/qRB8ZI5nDLh V5tRc982f8tp3+fTrjyynJb/2VwqYuCoGAbO5b12aAhReI110u7x8/PHQQqOpzXmSXFS aKs3GpLDevO0alrHdQqm1Dc5AQ3ONK8MfOBc3Gd8uaZx61aoiC/hylLLo+ID6NB27tiz IYTg== X-Gm-Message-State: ACrzQf11UuxGNM3Hwpm4dwxg5qbPCVAoFQa2kONm3PUksMBaAPMNtoZH JV4dP/F0fkZcC+/KgBWdvZ587mmYfjw= X-Google-Smtp-Source: AMsMyM4f9JeyduHGhueEbTJ4BZt+LE3bFmsy+D4KI6wopHUti5+qLhlDg8LV6bP0YGDGoQo0vJBxpg== X-Received: by 2002:a05:6512:2a8a:b0:49f:546b:6cd1 with SMTP id dt10-20020a0565122a8a00b0049f546b6cd1mr10103818lfb.422.1664275695343; Tue, 27 Sep 2022 03:48:15 -0700 (PDT) Received: from [192.168.0.101] (nat-0-0.nsk.sibset.net. [5.44.169.188]) by smtp.googlemail.com with ESMTPSA id d10-20020ac2544a000000b004948ddb4e4dsm124537lfn.301.2022.09.27.03.48.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 27 Sep 2022 03:48:14 -0700 (PDT) Message-ID: <63621195-babb-8599-7086-5a00976cff59@gmail.com> Date: Tue, 27 Sep 2022 17:48:13 +0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly) Content-Language: en-US To: emacs-orgmode@gnu.org References: <87o7v4iawb.fsf@mfa.pw> <87mtamjrft.fsf@localhost> <86k05pj3jo.fsf@gmail.com> Cc: Matt Beshara From: Max Nikulin In-Reply-To: <86k05pj3jo.fsf@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=2a00:1450:4864:20::12d; envelope-from=manikulin@gmail.com; helo=mail-lf1-x12d.google.com X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, NICE_REPLY_A=-2.319, 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=1664276046; 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=B1l/QHNeM/hDwhhDsOS8ie6nPd0MWTH7mC64jiZWYco=; b=cbCqDfaWUgXwFr+h5QDYb/nqh+rPVlDtK8qEZezdD9UjAiTScmWpY/AwWRN7bVG2EYqY+0 chSaeHMj3m/5w89PzMu1L7U39JQjDin7eVSKxGwia+k/63P17/9VbE3mPB5CdbCf0xtlSk n9njfYf0wNorD2lNN+GjCDZR8hhYEKpT5fzckE3ffa8iaD3RbVH77bmAEus+/9raDn7QFr A2IHlovka2oq9rrJ0syCcMhjnGw4L/dmiZFv1JLu1TaO9HFK/xplpf4Vf6MvI654cB6x6B /97oVoksfravGrQj4c1ocOfD/B8jhjlMQGSR+bFyPytoU05up/Dcgr3ZOVMs5A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1664276046; a=rsa-sha256; cv=none; b=OREy973zXPxCdaoWnssNtVuZInjKJ+lKfx696IeIoVSYH46U7Kd9+AEVYa6qGJjSATQh+G yj5cIYI44dHJtmBBtrj8ocJk0aL/HAwj+FIMqsbVX3lnGrtUyK6sUizYeXEoWEKTkZTqQR zLjVpb3f4tf5xV9sbzrzAJoEtCOu89+/xlECVweR2oqdiaZ8kzKUpwn5o+guD+Ziwd2kgi kHhyFC8MQtmVXRgZm2zeKxs03rxd0z+00Rb3irUpL1Xm/YqFTcT6VuUzlKG4Fqlw/q5n/s Aj0LvQShM1aWnhLFqIsOoh70KxXH1mp+37qiFcLAMimloq9GiPTNQxXjRDBU2A== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=l2H+cgAh; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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: 7.86 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=l2H+cgAh; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none); 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: 46CF12A38A X-Spam-Score: 7.86 X-Migadu-Scanner: scn1.migadu.com X-TUID: jGcpeQuclxP3 On 27/09/2022 03:13, Tim Cross wrote: > Max Nikulin writes: >> On 26/09/2022 18:39, Ihor Radchenko wrote: >>> Should we add page break (^L) to our syntax? It sounds like a reasonable >>> addition for a text-based markup. >> >> I do not have strong opinion. It is a control character while I prefer explicit markup and >> printable characters or commands in such case. On the other hand the character is widely >> used in .el files. >> >> Users may expect \newline when ^L is exported to LaTeX. > > I think I'm with you as well. I don't have a strong opinion and while > personally, I don't like control characters used as part of the syntax, > ^L is often used in elisp files, so ...... Matt, could you, please, provide some details concerning your use case for ^L in Org files? Even if nothing will change this time, it may affect later decisions. On 27/09/2022 13:21, Robert Klein wrote: > On Tue, 27 Sep 2022 01:10:49 +1000 > Matt Beshara wrote: >> Fair enough. If the consensus from others is that ^L should be >> recognised as a paragraph separator and the code is eventually >> written to make that work, that would be nice, but as it stands I >> can just start adding newlines after ^L. > > Actually ^L is a *page* separator (to be exact “FORM FEED”). I have realized that page separator for plain text is not necessary paragraph separator. The same paragraph may continue on the next page. It makes things more tricky. ^L should be kept on its own line while text around should be wrapped. However from a discussion happened a year ago I concluded that it may be not so trivial to tune `org-fill-element' for special cases. Timothy. Re: [PATCH] Don't fill displayed equations. Sun, 03 Oct 2021 16:50:54 +0800. https://list.orgmode.org/875yueij6r.fsf@gmail.com