From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.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 mEMLMhCEr2JSDQAAbAwnHQ (envelope-from ) for ; Sun, 19 Jun 2022 22:16:16 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id WEgFMhCEr2KhfQAA9RJhRA (envelope-from ) for ; Sun, 19 Jun 2022 22:16:16 +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 5DFF33D44B for ; Sun, 19 Jun 2022 22:16:16 +0200 (CEST) Received: from localhost ([::1]:44876 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o31LD-0000sA-EF for larch@yhetil.org; Sun, 19 Jun 2022 16:16:15 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:55450) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o31Kf-0000rw-I7 for emacs-orgmode@gnu.org; Sun, 19 Jun 2022 16:15:41 -0400 Received: from mout02.posteo.de ([185.67.36.66]:33381) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o31Kd-0001jE-KT for emacs-orgmode@gnu.org; Sun, 19 Jun 2022 16:15:41 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id AF4A0240117 for ; Sun, 19 Jun 2022 22:15:35 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1655669735; bh=oPYGje6EWsiYQFUKXE+Zgj235vgENtkv6btS3DxzNsM=; h=From:To:Cc:Subject:Date:From; b=TK98xE02tKJtLXOQgLVgpGSYVhjOVutIgZw9C8fNHQxQM9q/d77fu0iLQ2Uh/lOeb iIBX4lSnXBBghT65L7wfDYjow9HcJfohj+vCeG/tk9YMiE+C7G/QlLtL8g1hjor/Pf 9jgAf3cen3pE7JkD0k6SZa/DiRAbO5yGYzJOjfmJ7hHqZtbaQ17FMsjVvEaK27hBbS gbLZPmnHTUkw/z9mLjiuYYiaR9GpS7z88feotkLSvyaXARh4YqZzWw0cTKCvXPK+ZW jgq16/haPc0LUQ6Tczb4yYHsfValPSWAjALZpxxlm9b4z02SmgjbgnE7fT14RvX1Al 5XdTwzhiZtXBg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4LR3tS6bncz6tnM; Sun, 19 Jun 2022 22:15:28 +0200 (CEST) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Christian Moe Cc: orgmode Subject: Re: About 'inline special blocks' References: <87a6b8pbhg.fsf@posteo.net> <875ykwvmz7.fsf@posteo.net> <874k0gpi2h.fsf@christianmoe.com> Date: Sun, 19 Jun 2022 20:15:26 +0000 In-Reply-To: <874k0gpi2h.fsf@christianmoe.com> (Christian Moe's message of "Sun, 19 Jun 2022 21:30:14 +0200") Message-ID: <8735g0tnoh.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, RCVD_IN_MSPIKE_H2=-0.001, 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=1655669776; 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=vivXqvGV3V8dOB87U3qC91dvxlOpdulkapJ0y19LE6U=; b=QtaySpwFJx0XWGXBz86ovOKwUsmkwYOJGzMXzXhstg/mwPdfVRhVUtiL3PcnFTUOFffowy d+q+xbYJUsF4mspDPUbJd5OrfWJCLrUs+Nu6kdZoKD1azJZ7uVPRxkxDheQg7TOeaL4Jgb g4zAp+968eL6J6dWQ7Aw58yyV2On/Xe4SwA1NjEsY/e7XmBeITnBmPWuJOhusYY/VHp7rz ACGL0p2XiXsC1KeSR+T0NJgCB7SYkTEhzLfZfc0E2l/xN6xxfNOLCXo/21sZnhQxcWP7qh 1xxKGNTlCgglCXkZ1XPa9kbTBT40CNU9TB3SffhwNhbeiN5iMlk8YyoSGyDtRg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1655669776; a=rsa-sha256; cv=none; b=D+JYk+Tifwapd2MAK3ORsA/62czmY2YrCA52t3ZuezCVeRLxmkuax85cwEYPgCdYgCY/kH h8gsych5Mm9GAFVYfE7V/qMJOU/aNa8iOwmynRbHGTW8RISdrvL4MKW2Nf6gZJ/69EuleS EmMW0KUWoZUPM5l1vMQZV5IRJwTc39MZyd/mYkCqJvLwhOfEr3D2y1lEA6X7bHNXeuUs0M 4YhvqqDZ3XNhC34/BGYUrPmHmogwF1lydXKYUlDIhaZd3Ryg9+96jpXIfz6iqXHrFvls9k Mf549biuxzIhKB7Lm0Hs+qvtHeNexq87UVNNsMTB+n4sTUTDWVJk2wk8zLDSvA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=TK98xE02; 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: -5.48 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=TK98xE02; 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: 5DFF33D44B X-Spam-Score: -5.48 X-Migadu-Scanner: scn0.migadu.com X-TUID: exmyliF6y3Hm Hi, Christian, Thanks for your comments. Christian Moe writes: > Hi, > > This makes sense to me. > > Note: For the html output in your example, I expect you don't mean > contents>, but contents. That > would give the desired custom style controle of the output, and would > parallel the behavior of special blocks. You are absolutely right, it is my fault. These days I'm doing a work with a lot of xml, and I've mixed things up in my head :-). In html the expected form is as you say. Apologize for the confusion. > If "inline special blocks" will be able to nest, they will have an > advantage over org macros, which cannot. > > Apart from nesting, an org macro could do the same job, but less > elegantly. The suggested inline syntax would not require commas to be > escaped in the contents. And it would be somewhat more concise and far > more legible, as illustrated in the below example (with working macros, > imagined inline special blocks, and a CSS implementation): > > #+begin_example > #+macro: fmt @@html:$2@@@@latex:\$1{$2}@@@@odt:$2@@ > #+html_head: > > This is some {{{fmt(highlight, highlighted text)}}} and this is some > {{{fmt(smallcaps, text in small caps)}}}. > > This is some %[highlight]{highlighted text} and this is some > %[smallcaps]{text in small caps}. > #+end_example I have used macros a lot in the past for these purposes. But the problem of having to escape commas and the somewhat confusing (and ugly) syntax of macros has led me to rarely use them now. Links have been a good replacement for me, but they still have their limitations (the most important, as Ihor commented, not being able to include a link within the description. But we can't put footnotes either). I actually think that inline special blocks could be tremendously useful and versatile. And, in syntactic terms, an important point in favor of Org against Markdown, which if I'm not mistaken does not have anything similar (I hardly use md, so I'm not very aware). Best regards, Juan Manuel