From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id aAfpARI+kGOqFAEAbAwnHQ (envelope-from ) for ; Wed, 07 Dec 2022 08:17:38 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 8ATDARI+kGPN2gAAauVa8A (envelope-from ) for ; Wed, 07 Dec 2022 08:17:38 +0100 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 AB9BA22CBE for ; Wed, 7 Dec 2022 08:17:37 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p2ofU-00057j-RQ; Wed, 07 Dec 2022 02:16:36 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p2ofS-00056s-GI for emacs-orgmode@gnu.org; Wed, 07 Dec 2022 02:16:34 -0500 Received: from udcm-wwu1.uni-muenster.de ([128.176.118.7]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p2ofP-0006Fg-BL for emacs-orgmode@gnu.org; Wed, 07 Dec 2022 02:16:34 -0500 X-IronPort-AV: E=Sophos;i="5.96,223,1665439200"; d="scan'208";a="219412979" Received: from wiwi-ex-1.wiwi.uni-muenster.de (HELO mail.wiwi.uni-muenster.de) ([10.2.21.33]) by UDCM-RELAY1.UNI-MUENSTER.DE with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 07 Dec 2022 08:16:27 +0100 Received: from D-3170L03 (128.176.63.9) by WIWI-EX-1.WIWI.UNI-MUENSTER.DE (10.2.21.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.16; Wed, 7 Dec 2022 08:16:26 +0100 From: Jens Lechtenboerger To: Max Nikulin CC: Subject: Re: Syntax question: What is BORDER in 4.17. Text Markup? In-Reply-To: (Max Nikulin's message of "Wed, 7 Dec 2022 10:35:38 +0700") References: <87mt80e69n.fsf@wi.uni-muenster.de> Mail-Followup-To: Max Nikulin , Date: Wed, 7 Dec 2022 08:16:26 +0100 Message-ID: <87fsdrr8dx.fsf@wi.uni-muenster.de> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Originating-IP: [128.176.63.9] X-ClientProxiedBy: WIWI-EX-2.WIWI.UNI-MUENSTER.DE (10.2.21.35) To WIWI-EX-1.WIWI.UNI-MUENSTER.DE (10.2.21.33) Received-SPF: pass client-ip=128.176.118.7; envelope-from=Jens.Lechtenboerger@wi.uni-muenster.de; helo=UDCM-WWU1.UNI-MUENSTER.DE X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1670397457; 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; bh=KkYmArJsd5hYrQtZS2Z8qBJxxOFNRNESKbMeoVH4LIE=; b=OqW2rAOs5expuLewISVqHEu2AoenmHiwDNekOC/YHzqnojqqJsZWc7biTyRtskE3YUYO4v 4vUI7leAT896jzacOZ/q9Rmx50JDCL7w+SIosdO+qxZV/pGCBo7jCW45ko3Ccdbt39poKN fFE5DIvNt77yWVla92/niNF3BOEQMM8exs0I0GWlXPfE8f0kPikGI++AEXXD7G2oLktwMH adaU0yvT3IkMVXIbI8/if8rfQZhN6Bwa0w8Bk8Iv5mcvnLKJlPp81Hsg1ER9YDbda4W+w5 UKhZroL+oUz6bN5Mb48ipDBlOXoDArFs+yQLYg4Em5VyAmTEt/+q9k3LhQjnDA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1670397457; a=rsa-sha256; cv=none; b=BRh7hdLmSrzIxsTMmq+1jCX7tQw/1yBKdTywU/QzyMunY5DyowLEfcXAxSbiJ3VCMZNXl3 HplD39gJeZWo38lMnpkAP8DMERWSp7OaRFa2dGWUJ1xOprfamW3MW4BpzESOCmcHI+vJfP Z3PPRLl3TOOr7XtVcXmps4zUYVwWoBTIxKYhZ/AcNeaWpZsO49/NNSD7CxHtRSVASngHDb /gxativLvjpPzOvrDfGZVb2vNX4tHFkvpwhOZkFUzDKmk+ZsoD6aHDOBPrH1QLbbANNEwh NRQdz5DaLs8s0HQCW30YFL+bEt7p/xOAhS5OKO2LdLM5VLqija4PBWNDLWG5vQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=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: -3.07 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=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: AB9BA22CBE X-Spam-Score: -3.07 X-Migadu-Scanner: scn0.migadu.com X-TUID: PJh/DEpb1ok2 On 2022-12-07, Max Nikulin wrote: > On 07/12/2022 01:28, Jens Lechtenboerger wrote: >> Hi there, >> the syntax for Text Markup such as *bold* at [1] specifies >> PRE MARKER CONTENTS MARKER POST with >> CONTENTS as BORDER BODY BORDER and >> BORDER as =E2=80=9CAny non-whitespace character.=E2=80=9D >> What is the role of BORDER here? Does it really exist? > > I think, the idea is to stress that > > / / or * word * > > must not be considered as emphasis. I see, thanks. >> What is BORDER if CONTENTS should be a single character, e.g., in >> the two strings =E2=80=9C*x*=E2=80=9D and =E2=80=9C~*~=E2=80=9D? Are si= ngle characters forbidden? > > The spec is not precise here. It is close to the code that actually > allows single character contents, see > `org-element--parse-generic-emphasis' and the docstring of > `org-emphasis-regexp-components'. > > Perhaps it should be stated as (in regexp notation) > > BORDER (BODY? BORDER)? > > or as alternatives > > BORDER or BORDER BORDER or BORDER BODY BORDER. If find this confusing. What is BODY (semantically) if two of its characters are assigned to BORDERs? What about getting rid of BORDER in the spec and replacing =E2=80=9CWhere BORDER and BODY are not separated by whitespace.=E2=80=9D with =E2=80=9CWhere BODY does neither begin nor end with whitespace=E2=80=9D? (If that is correct...) The implementation with regexps is a different issue. Best wishes Jens