From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.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 oEfAFrxn+2PadQAAbAwnHQ (envelope-from ) for ; Sun, 26 Feb 2023 15:07:56 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id 2G+cFrxn+2PdRgEAauVa8A (envelope-from ) for ; Sun, 26 Feb 2023 15:07:56 +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 C8DFD3AF3F for ; Sun, 26 Feb 2023 15:07:55 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pWHfs-0002ye-38; Sun, 26 Feb 2023 09:06:48 -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 1pWHfi-0002wr-VX for emacs-orgmode@gnu.org; Sun, 26 Feb 2023 09:06:40 -0500 Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pWHfg-0005eQ-Je for emacs-orgmode@gnu.org; Sun, 26 Feb 2023 09:06:38 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 20AC6240081 for ; Sun, 26 Feb 2023 15:06:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.eu; s=2017; t=1677420394; bh=4EWNi4pDWnKt4KzpNgGN8AbeP/S9u1XqcS+NXlrlOZQ=; h=Date:Subject:To:From:Cc:From; b=B/CDaOH6047UN+GsPbxXXdT4AvwEfn8ENtni973OmnulBkmgO6M3zNYC+fOrx0csS VJ7XIVPOqtI2ivrKlMukq+2fBCJ3+l1Vq5kYO/c9RRkcjxP2KUqnGKIELQ9raw8rrh OUJWoBlD65oeSRgQHX8L4T7Xlpt5FvMxBPQGfW38uw5+J7N+NSOVVU7iprk7oKJNiO rNIM1ZOVsDyWUvQ9E1RDM4Kjau70MdtUCk2InlYA8tlYUGgGZV2GYy4YFp4YAeWJ8g ag0dzWk04gDm+H7pOQSveZW/HJYA8LFSK/Ajv8fZdER/er5WaBWX8XNI5EYJ74ERPt 2Krrp+7Lx4b+Q== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4PPlmT0tWpz9rxB; Sun, 26 Feb 2023 15:06:33 +0100 (CET) Message-ID: <4cf06875-2494-9a17-8c6a-b4bd9449b28b@posteo.eu> Date: Sun, 26 Feb 2023 14:06:32 +0000 MIME-Version: 1.0 Subject: Re: [POLL] Naming of "export features" Content-Language: fr To: Ihor Radchenko References: <875yc95rxp.fsf@tec.tecosaur.net> <87h6vfnl3a.fsf@tec.tecosaur.net> <871qmhdh3l.fsf@localhost> <27a9349f-2171-d065-d257-6074f627c1ef@posteo.eu> <874jrbs6iv.fsf@localhost> <87edqf43m0.fsf@localhost> <2e2828cc-95c7-f895-dfd8-e524c850e7ca@posteo.eu> <87fsaszk48.fsf@localhost> From: =?UTF-8?Q?S=c3=a9bastien_Miquel?= Cc: emacs-orgmode In-Reply-To: <87fsaszk48.fsf@localhost> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=185.67.36.65; envelope-from=sebastien.miquel@posteo.eu; helo=mout01.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 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: , Reply-To: sebastien.miquel@posteo.eu 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 ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b="B/CDaOH6"; 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.eu ARC-Seal: i=1; s=key1; d=yhetil.org; t=1677420476; a=rsa-sha256; cv=none; b=fc5AtCmMxLEKjkLWLF+Ra1uX94RO1Ti0/p+e4nd4jLBfIQiTjokEGM4Ieho74l4uTgQnLH rEgmgDUvbb+dMHW90y/ZCZ/aM+lnQpCc6U9bAilJW4Z+DknA8iY5iauldqGyQ1Xod2D9rg OBZKHZ4edFVHx0Lbj2DjrpwJ7DpTZWV7BNPdmyw0c8r3+fxM4pWrkpKgLpl0q+/zf8MRW6 Xt0ujQOCFup3BXmdInnglfM44hO/SOZ2vNJDpwbt48//Hp+a7ia2+hGrhU17zMVGbuH9vs reKvmNU341TxS5WSTHOmUng8IyncCP8+DMLD6t7N6r8LLfHHNZSTZd+X2UuwTQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1677420476; h=from:from:sender:sender:reply-to: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=GhKJU3m3R+ap6RtWVGOjFqvJJ06ZKHIotGWs7dDe8F0=; b=OPNds3BBU5S6S82n2bnAh5teP3I8e8gdCriXxo/QNCOCSlNmYnntsG/0L+iKdcJCeAeCBA cPQqHiBhvz9lE1ahhZ4FNqeDyySY11NVJEpzHUekMLoCk5LOFbcqwhSi7V+fBDUPxZD5rk MbvlAtxNpWxkOx+on98wx8M2Qm4HwpwDTkb4RpPtOQ2g1pVR9FdWcbE7BDpvVy5Fgq7SRE ndlzPIT/+1lgnpX0VI2U6f5AsFuxuxeDPUDjg+BwlBGND+0FPrZ29lr7q6UIvW+bTJi/EM 59YPnwRLPEt1/55dJqNPaevefQt+TlHeZ3AX88bREGPMYXYyyD7LhDE008Lr+Q== X-Migadu-Queue-Id: C8DFD3AF3F Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.eu header.s=2017 header.b="B/CDaOH6"; 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.eu X-Migadu-Spam-Score: -7.39 X-Migadu-Scanner: scn1.migadu.com X-Spam-Score: -7.39 X-TUID: FNSqzKavePmJ Ihor Radchenko writes: > Only the simplest cases of prepending/appending staff. > If we want to splice into the normal export template, users currently > must either write an output filter or rewrite the trnascoders > completely. > > The proposed template system will provide more flexibility to modify the > default export transcoders. Reading your original proposal, I see nothing that provides more flexibility. I can guess at how it would allow one to prepend/append stuff to the output of the default transcoder. Anything more flexible than that would require breaking these default transcoders into parts, which you did not originally mention. >> Here's a couple interesting examples that currently cannot, I think. >> + a `multicol` heading property, that wraps the content of the >> heading in a multicol environment. > Could you please illustrate with examples? Exported content would be: #+BEGIN_SRC latex \section{ABC} \begin{multicols}{3} Section content \end{multicols} #+END_SRC >> + a `nocontent` property that do not export the content of the >> heading > This can be done with :filter-parse-tree or :filter-headline I guess. This isn't "couple of lines"-easy though. >> + Some way to play with the numbering of section, beyond the >> `unumbered` property. > Could you elaborate what kind of "play" you are referring to? I cannot think of anything that cannot be achieved through (somewhat fragile) post-processing with `:filter-headline`. Anyway, I was only trying to understand if your proposal could easily do these things. What flexibility does it bring ? >> It is indeed unfortunate that org doesn't provide an easy way to get >> this behaviour, and achieving it would require the fragmentation >> (templating ?) of at least some transcoders. I'm not sure that it >> makes sense to do this for anything other than the headings >> transcoders, and the main template. > Currently, transcoders are opaque functions that expose a limited number > of pre-defined settings. Turning them into templates will allow certain > non-standard alternations that we cannot think of in advance. Without > directly modifying the transcoder function code. > >> However, this seems orthogonal to your previous proposal. It is not >> clear to me how it ties with your syntax. > Could you elaborate? See higher. More flexibility requires breaking up some transcoders into pieces. AFAIU it, the proposal you originally described does not bring any more flexibility beyond what can be done through short advices, or indeed the `:filter-` functions. I'm not sure this dedicated syntax is preferable to advices. -- Sébastien Miquel