From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:c151::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id wOZRB5/5MmASMQAA0tVLHw (envelope-from ) for ; Mon, 22 Feb 2021 00:23:59 +0000 Received: from aspmx2.migadu.com ([2001:41d0:2:c151::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id sHf4Ap/5MmDbIgAAbx9fmQ (envelope-from ) for ; Mon, 22 Feb 2021 00:23:59 +0000 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 aspmx2.migadu.com (Postfix) with ESMTPS id 58DD623554 for ; Mon, 22 Feb 2021 01:23:58 +0100 (CET) Received: from localhost ([::1]:34852 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lDz12-00076e-Ua for larch@yhetil.org; Sun, 21 Feb 2021 19:23:56 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:58242) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lDyz7-0005qP-PM for emacs-orgmode@gnu.org; Sun, 21 Feb 2021 19:21:58 -0500 Received: from mout02.posteo.de ([185.67.36.66]:52457) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lDyz5-0006SG-MA for emacs-orgmode@gnu.org; Sun, 21 Feb 2021 19:21:57 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id AF07E2400FB for ; Mon, 22 Feb 2021 01:21:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1613953312; bh=ZdqrKWMzzC3lzEwtjT8n5pxnMRrMenpTZASlzASexg4=; h=From:To:Cc:Subject:Date:From; b=JVh/jkHxZmaxjo3EOrn45NkfZ4Va+BuRgkWyQyEpcGDvYwy5h877uPqUPr0DlrmLz VbpbfDvPtLqtGZA0xfSwBHPaQXGnguLrhlvSP0FxKXEkIGAFqedTne7KSEUN/srH7R B3D9yGnmNuc4RZ/FCFB95juaKDOFiOmtHHU34fdIqfBrY1lBiJxqFGDM0r1RX3dQL4 KwLPUXpC0WMn5cpcY8be1cTz8rxuy/Sk5pH5XYSn81Iicdl3Sgg0dNN1XjRAFKEac8 24b3EZ40URUksd1Ue8RhmRxLiNclsTV5Lb5Lo+ZWvMuFBcKXquJl7deF5zqDpnXHtM WsJxYkFH7vp/A== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4DkNCg6jjYz6tmD; Mon, 22 Feb 2021 01:21:51 +0100 (CET) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Tim Cross Subject: Re: 'false' list item References: <87ft1xfd01.fsf@posteo.net> <87pn0tj4dt.fsf@kyleam.com> <87mtvxrzan.fsf@posteo.net> <87wnv1do1t.fsf@gmail.com> Date: Mon, 22 Feb 2021 01:21:51 +0100 In-Reply-To: <87wnv1do1t.fsf@gmail.com> (Tim Cross's message of "Mon, 22 Feb 2021 09:31:57 +1100") Message-ID: <87v9alq7ds.fsf@posteo.net> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=185.67.36.66; envelope-from=maciaschain@posteo.net; helo=mout02.posteo.de 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: orgmode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.07 Authentication-Results: aspmx2.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="JVh/jkHx"; dmarc=pass (policy=none) header.from=posteo.net; spf=pass (aspmx2.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 58DD623554 X-Spam-Score: -3.07 X-Migadu-Scanner: scn0.migadu.com X-TUID: jJpo/sciqLzZ Tim Cross writes: > The issue is, if we decide this is a bug, can we fix it? Is it a bug or > is it just an accepted limitation of the org document format and what we > have to do is ensure either no line starts with a '1. ' or we use > something like a unicode character so that it doesn't look like a > number+period+space and therefore not a list item? Interesting all the points you comment, and this paragraph is important. I'm thinking that without a clear and explicit environment (a begin/end marks), any possible solution will always have its exceptions. However, IMHO, I would not find desirable two explicit marks environment in the style of LaTeX, since this would go against the virtue of legibility and lightness in Org. I don't know if Markdown (on what it has in common with Org as a lightweight markup language) also has similar problems in lists formatting, since I hardly use Markdown and am not aware of its many implementations... I still think that highlighting the items would at least be a preventive solution for Org. Best regards, Juan Manuel