From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id CLnNFrH5i2IWywAAbAwnHQ (envelope-from ) for ; Mon, 23 May 2022 23:16:33 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id eEX/FbH5i2KEFgEAG6o9tA (envelope-from ) for ; Mon, 23 May 2022 23:16:33 +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 044863FB2B for ; Mon, 23 May 2022 23:16:33 +0200 (CEST) Received: from localhost ([::1]:52416 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ntFPk-00038Y-66 for larch@yhetil.org; Mon, 23 May 2022 17:16:32 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45902) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntFGQ-0007Su-44 for emacs-orgmode@gnu.org; Mon, 23 May 2022 17:06:54 -0400 Received: from mout02.posteo.de ([185.67.36.66]:37953) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ntFGN-0007w3-Ch for emacs-orgmode@gnu.org; Mon, 23 May 2022 17:06:53 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 469AD240109 for ; Mon, 23 May 2022 23:06:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1653340009; bh=w+XQCi+UWF6OU8BbFNc34J9xFNcUPld9PZjR8icg4Bo=; h=From:To:Cc:Subject:Date:From; b=W9pN+F4BV6T2tcj7yfZC9VPmeV+fIkDrKbOQzDFvOnEqLTWuyXp0Is7J2DC7tY1Ra nGVyMmkNovqDsEnNAtKCsz0u9ky6PUAYY2CWI7b5cj85WxanwVPmvMwcMc4jhLJ9oc 8r2fCtj/w9gaC4ynZ0zs7F10EoKex2i3ji8nbeHfKTumdgQQ+KZfIbGmEY7Ix7v5Fq IoSbc+jNVosEz55IFDeBFL0u5MKwanf9YDsHDlPFU9ZuEkO7URMN7Xxz84d7gAeaCg 3uMuu1+sgw1doRrecJCJLspDA2FJYbovHY13687eVpVj2WTkfP4EzpPeDbzjl2OLIQ fIlYxSv4k3Fkg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4L6VJ84j0zz6tm6; Mon, 23 May 2022 23:06:48 +0200 (CEST) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Kaushal Modi Cc: orgmode Subject: Re: About 'inline special blocks' References: <87a6b8pbhg.fsf@posteo.net> Date: Mon, 23 May 2022 21:06:45 +0000 In-Reply-To: (Kaushal Modi's message of "Mon, 23 May 2022 11:20:08 -0400") Message-ID: <87czg49cwq.fsf@posteo.net> 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, 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: 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=1653340593; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=bQAIkfzhd5eC31iVKEKDsNo+MrOKJZmx3h/ojiBWOCk=; b=X15MEQKteXIxLbIk0+OOcXYdSSJStFjPCQXBb08g3kUN4Ov28YObYK6PWYlkxB0HsiqS4r bpnkWcIqRMMOUNy3/DDwcjMezdt4Sf55xmfFwTvGf5JPOexUHP30rjU313U6J3m8zmKyCR RwVdPYw9EhW6jkKr3zxV8+fumdg40lUAKOVch3p4lxZFHkvXY3/hy/+QDSAASm/YQdwLC7 MnMckx64AXdAZtGlEgLb6P1jaxl0eARMTZ/cUYG+lLzarXSdme4v9SgqMtsiuMZsDc5HT+ MqK82nphAu1fiS0+XQB/SCokZftfjGw/6t0Lw2/USm4UbYq003Ei0DdV4p2v6A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1653340593; a=rsa-sha256; cv=none; b=WYON3AS1Uz0lGG7QPxMCLUO7vltTXgJt2RUfpRFZ6Iu0IbtmXy9n0GHuZ9G+6AomvpSEbV 04kWQwW/TO7LE8zK8rr0GaPTEBY58pq4E0aMAgV7EThQ/RYeGOlqOvhJo5wR33ECUiNaYi o8dwnya2R8CZLGa/5yKo1vmCUWAHZPlFR6yWyGkREEFKCt2VAQw1lefYyXBElZBT8dVIEH gtH3LGRKMJ3QwyomTwP/lHcoO4JwOv1ZiaGaGA5R4c/exKkpXtfP85oHE9Fxsp6uSo3Ihq 4EVbHKABzAa16LHqqDGaouttRFTO4JXDgM8qHc4j6FZvlhPAz4H1npctrZjQwA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=W9pN+F4B; dmarc=pass (policy=none) header.from=posteo.net; 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.75 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=W9pN+F4B; dmarc=pass (policy=none) header.from=posteo.net; 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: 044863FB2B X-Spam-Score: -2.75 X-Migadu-Scanner: scn1.migadu.com X-TUID: LtG1tb2u/518 Hi, Kaushal, thanks for all your interesting comments, Kaushal Modi writes: > The challenging part will be deciding the syntax so that there are no > false matches. > > May be reserve "inline_" for inline blocks? > > e.g. inline_[options]{text} ? It seems to me the most consistent option, if we continue in some way the syntax of the inline code blocks, which would be the close relatives of the inline special blocks. Perhaps (to shorten the syntax a bit) 'inline' could be replaced by some reserved symbol. Something like: &_[options]{text} I think a major issue would also be how to properly compact <[options]> so as not to result in too overloaded syntax. Maybe something like: [latex(list of attributes) html(list of attributes)...] ? But that is an abuse of direct formatting, which I think should always be avoided, especially in a format-agnostic environment like Org, which is more of a logician than a typesetter :-) And, in any case, it is to be expected that the user will not need to overload that part, since these hypothetical inline blocks would be intended for short segments of text within the paragraph. I think the most typical use case would be something like your 'mark' example. Best regards, Juan Manuel