From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id wC8jMwDB+mGVdAEAgWs5BA (envelope-from ) for ; Wed, 02 Feb 2022 18:36:00 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id QNjoKwDB+mEm+AAAG6o9tA (envelope-from ) for ; Wed, 02 Feb 2022 18:36:00 +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 72F9C3BD1E for ; Wed, 2 Feb 2022 18:36:00 +0100 (CET) Received: from localhost ([::1]:52190 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nFJXz-0005EO-Ef for larch@yhetil.org; Wed, 02 Feb 2022 12:35:59 -0500 Received: from eggs.gnu.org ([209.51.188.92]:48498) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFHZG-0000V3-Qo for emacs-orgmode@gnu.org; Wed, 02 Feb 2022 10:29:10 -0500 Received: from ciao.gmane.io ([116.202.254.214]:36324) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFHZF-0004g0-4Y for emacs-orgmode@gnu.org; Wed, 02 Feb 2022 10:29:10 -0500 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1nFHZB-0004uJ-28 for emacs-orgmode@gnu.org; Wed, 02 Feb 2022 16:29:05 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Max Nikulin Subject: Re: Org-syntax: Intra-word markup Date: Wed, 2 Feb 2022 22:28:55 +0700 Message-ID: References: <4897bc60-b74f-ccfd-e13e-9b89a1194fdf@mailbox.org> <87fsrbp673.fsf@gmail.com> <1ef0e093-c165-2a5f-954d-6a33b64c8ee9@mailbox.org> <87r1avgnpi.fsf@localhost> <878rx2bzhw.fsf@nicolasgoaziou.fr> <9525e029-a590-3f48-df64-ffb9176075d9@mailbox.org> <87v904nq6t.fsf@gmail.com> <868df76e-69e0-1d14-ae8a-13b746982fcf@gmail.com> <87zgnfgros.fsf@localhost> <871r0q8zg6.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US In-Reply-To: <871r0q8zg6.fsf@posteo.net> Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: 28 X-Spam_score: 2.8 X-Spam_bar: ++ X-Spam_report: (2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1643823360; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to: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=aH4rJeVyRQDjHdYCFDogzblAa/0wmQqWB6XVTblKAF4=; b=OHu0dBiEVs6d+TSye1jSEM4r7wy3ds3MlJ13lOwpQFOWkSta9RNTF3yM0qK4fhxBcJ17ur +9ZCrSYrCUG/3B+Y6mGcd20PFH7Gv2yfwhqzrvr4bar/Q9uQQy7YDjJxTIKIxKZvh7gwAA JS2g+FV3bsUfGL+px+2OPqPijFD4DUGZ9ZP4/dQYwFDsegCf+7OX9/QqTFFcEOTfOg2k9s IonddVaXABnqtchKASTGglz0W5h5fnHEHE7pbME/eW/JDJ7r6Rjz4OL8VGtflPhmRtCpB6 Jn+CmGKxiKntyTbUzlgsYb4CW4P8ZO7s2qDFWmaI/X3SkUQlC8HpXb2NzPaxag== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1643823360; a=rsa-sha256; cv=none; b=dy5pmaHk27LoSws3kBc5hBi1ZERWz4dEMFo90Ndae3iJr538X7tdizNcPfimM8bdaQUxrq SUjjPDM4zgaP8b2sq5yZdBGmwnLI6sK3UNxkyZYJyhkFMpTa6Px51EZmyrSxgUg8uKMWD6 iELx/XBvAvO1//yBWsZZ0xVWruuj0UhiH0VQGnkM8jiMAnxE+ej9TvZviBJF6pkix4qyiD sLsD/Xd95RfQbLUevGiLfpQn/rf8vvelhfmg8UcEYh5NXN2MZH7lbk9p0FYMEkn6/IGXN/ TMbs3QM/lDosJOxpFxhDBoat38JXTkPImrpxO0Rx4Wb/gwgcdmAREUjIaGuQrg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" 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: -2.53 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" 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: 72F9C3BD1E X-Spam-Score: -2.53 X-Migadu-Scanner: scn1.migadu.com X-TUID: UqfMkEXSoMVF > Ihor Radchenko writes: >> Keeping in mind the above analogy, note that export blocks do not have >> fallbacks, while special blocks do (for example, see >> https://github.com/alhassy/org-special-block-extras/) Ihor, I am sorry, but I missed your point. That project provides some set of defined link+block pairs and some macros to define new links/pairs. I do not see relation to export snippets or blocks that are used when their content is not intended to be reusable. >> Maybe we should introduce an equivalent of special blocks, but for >> inline use? Or should we modify _both_ inline export snippets and export >> blocks to allow fallback mechanism? I suppose, it should be consistent to consider adjacent export blocks as alternatives and to allow "fallback" or "default" block. Again, similar to @@:...@@ snippets, block content should be parsed as Org markup. On 29/01/2022 20:05, Juan Manuel Macías wrote: > I find the idea of inline special blocks very interesting, but I think > there are a couple of drawbacks: since special blocks support ATTR_X, > how would that be implemented in the inline version? The most obvious > thing I can think of is to mimic inline code blocks: > > my_special_block[attributes list]{content} ATTR_X attributes are supported for links as well, see info "(org) Links in HTML export" https://orgmode.org/manual/Links-in-HTML-export.html However it is rather verbose, may have problems with LaTeX, and I am unsure if they can be accessed from export link handlers Actually I do not like src_something[...]{...} syntax since there is no clear mark (such as "\") at the beginning that it is a special construct. > In any case, for things like that, aren't links and macros enough? Ad hoc code for particular backends (and discussed fallback for other backends) is a bit different thing. It may be used in macros, but macros can not replace it. Moreover @@:...@@ construct proposed by Tom would allow e.g. [[https://orgmode.org][@@:*inter*@@@@:/word/@@]] to be half-word bold and half-word italics without invisible zero width spaces and filters to remove them.