From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id 2DqiExNM1mUyIgAAqHPOHw:P1 (envelope-from ) for ; Wed, 21 Feb 2024 20:16:35 +0100 Received: from aspmx1.migadu.com ([2001:41d0:303:e224::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id 2DqiExNM1mUyIgAAqHPOHw (envelope-from ) for ; Wed, 21 Feb 2024 20:16:35 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="QEmzZM/B"; 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"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1708530106; 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:dkim-signature; bh=2u1P121AsU6gvLLypgtPfXkRfRiOITecehVe0MWCvgE=; b=ln9P/agpi/oQoLNm0jt40j2fsUiuGnprh/7XrZiHsOi5DWzmhnOS4bXE975v1dGMf/1BMH 9rg/R8cOmQqBAX1BJNn0f+zfP+mCyvb07L8Nf6Oksb+UwbZBvkXuNEhXhi1VL8G0btehqB y9sUI0brlWlEf3KIMVMpCLBI8NnJ7Auwz3OHhWrjtnXdv0N07CieALmj6bvNUIKiMFJesh y1C8H15M7LQuqNhjQuZYcJ7EkyiirJgRpInDIa+SPwdBVIRWL2te/I1W1hGTQe1vH54PJ/ IAAOiA3KK2DxA2rfwDS8MeXowqm6JxMgrmyw48wrpIJlKlyqBX22uLPrWQ6zFg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b="QEmzZM/B"; 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"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1708530106; a=rsa-sha256; cv=none; b=JlN57w74rKN5+PhfCUxI2EImYQMwCLsij5CCePMHYaDWm+LjDOGrVAlKTo2pFHm60VbEh1 AWPhhme4+IcK9tJSfhYW5lAwZzxDoR0o5MItvnLSg9gm/h291MI/NkBOe9fbJCdzhDhTSl RjFwQ6dSXLpADMaBIeNUnVrO8b0NTESP81AYL0dHap3TSqdWk3Mhwf9kEVLOZO+YjxDVOZ FNtj7/yG/4srHITW15QM7zxX3YjiFMEESk6G/I3wm8Pe9Y2cA8c/nWgdNfccuqg2B4HNA8 eyGM9CyzTFwsSqqBnVXUUuFsxPM8cpfh9EIke07fSY6UarB6SkG0UhAp15z5jg== 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 A3E48139FC for ; Wed, 21 Feb 2024 16:41:46 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rcoON-0001SO-P7; Wed, 21 Feb 2024 10:20:15 -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 1rcoKR-0000sX-Sh for emacs-orgmode@gnu.org; Wed, 21 Feb 2024 10:16:15 -0500 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rcmIm-00049S-Im for emacs-orgmode@gnu.org; Wed, 21 Feb 2024 08:06:35 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 3919D240103 for ; Wed, 21 Feb 2024 14:06:17 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1708520778; bh=2u1P121AsU6gvLLypgtPfXkRfRiOITecehVe0MWCvgE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=QEmzZM/B1nLiEuD/fo9zVE2cVfJzm5I4JumAMSZr55y3VyJjMByEpYymH2W0hp0Vy 7+R7urt73V+jh5R4Vvmkd3Qe/Z82VpAhqD/pfeZJZP3lRWHfejyvQgUe80tbfVHHnP EiK6TvxNHAP6HSyrnGcra+fvPeyurKCFuY8IrTIZZCi1p9WepAKmYTfc45uF1BIsIm t7O0CN+6udfY3pPcCg/ztDgBNFIz3FFEy/FwlFGdUKtvP4IRCRVA1ad/n3axCcdvDl PwCN71zPeoKc7bTiDaeUJq95clPVmt8Q91TPoINz4ZrAHM0d7rLmPHYprUyHcXCzJL Dt8im3mMtB8Aw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TfxNn2BkHz9rxB; Wed, 21 Feb 2024 14:06:17 +0100 (CET) From: Ihor Radchenko To: Juan Manuel =?utf-8?Q?Mac=C3=ADas?= Cc: orgmode Subject: Re: [proof of concept] inline language blocks In-Reply-To: <87a5nuyo4w.fsf@posteo.net> References: <87msrudgcn.fsf@posteo.net> <8734tmmcnv.fsf@localhost> <87edd6ytiy.fsf@posteo.net> <87sf1mrpr6.fsf@localhost> <87a5nuyo4w.fsf@posteo.net> Date: Wed, 21 Feb 2024 13:10:00 +0000 Message-ID: <87frxmrmjb.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=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-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx12.migadu.com X-Migadu-Spam-Score: -7.67 X-Spam-Score: -7.67 X-Migadu-Queue-Id: A3E48139FC X-TUID: 4THcRZGWitx/ Juan Manuel Mac=C3=ADas writes: >> We need to finalize inline special block syntax first, and then talk >> about special cases like inline language markup you propose. > > As I already said, in my local branch I have both elements created, > based on the same syntax: > > - language block: :lang{text} > > - special block &type{text} > > the latter would be exported, for example, to html as text or to LaTeX as \type{text} > > I like the syntax because it is minimalist and not verbose at all. That > could serve as a basis (at least it is good to have a starting point, > because otherwise everything will be diluted in discussions). Then we > can start thinking about whether to add options and how to add them. We do not need to design the inline special block markup fully to introduce it. However, we do need to make sure that whatever simple version of inline markup we introduce does not prevent further planned extensions. My main concern is the possibility to introduce multi-argument markup. Like @abbrev{EA}{example abbreviation}. This will be necessary to achieve parity with Texinfo markup. However, it is not yet clear about the best syntax to pass multiple arguments. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at