From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id yM8SMcfI8V9VIgAA0tVLHw (envelope-from ) for ; Sun, 03 Jan 2021 13:38:15 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id eBt8LMfI8V8IRQAAbx9fmQ (envelope-from ) for ; Sun, 03 Jan 2021 13:38:15 +0000 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 434C09403D5 for ; Sun, 3 Jan 2021 13:38:15 +0000 (UTC) Received: from localhost ([::1]:33770 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kw3aH-000417-Ot for larch@yhetil.org; Sun, 03 Jan 2021 08:38:13 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:40084) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kw3ZI-0003zg-OE for emacs-orgmode@gnu.org; Sun, 03 Jan 2021 08:37:12 -0500 Received: from mail-pl1-x632.google.com ([2607:f8b0:4864:20::632]:45839) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kw3ZH-0004zB-5C for emacs-orgmode@gnu.org; Sun, 03 Jan 2021 08:37:12 -0500 Received: by mail-pl1-x632.google.com with SMTP id e2so12982782plt.12 for ; Sun, 03 Jan 2021 05:37:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version:content-transfer-encoding; bh=m8T/6ZEuzwg3+9H5WOD+9FOTvVlq/WA8UnsjD8zRmv8=; b=gMrrFhwESz2qrMHsKjxOLLk4Ef3zjvxCCuNISfV0+PfiPbATf+9+Hwq6B8nyd6jqG1 m7iwGK/7JZFYZOR79vdrqU6fQJjv6sYsGbUUSKfq6bopL+h/T4i7bywTjUA3yyqCDOxi i4TpHnUez4oLdXJtD3HKtuKI0XLSMnEqsxMqFS7Jft4aUp0lznw1uvHtEJyNct5O3JeE G8cCtLm2rJikp1SdKin/WVFaxeFf//1MpGH2HR7Pln5KAsIXmBK99aPcy+uBEE3sLvBS 5P6Q+5A4CJP3VTha2UEtPycltt7Fy98QHVMD8n+3LB3Z0MzhvMNvCpRWO1Q/ZP25/Ei1 OMKw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject:date :in-reply-to:message-id:mime-version:content-transfer-encoding; bh=m8T/6ZEuzwg3+9H5WOD+9FOTvVlq/WA8UnsjD8zRmv8=; b=ITIICPXrOgBW1fekV8YBgxPNjDfbp9fgtkknWzWga+n2+ICLN7efgKPsI3MU+tiJAM KkKiLHReche1AL4YSC80F8DWtdqpHA7JkGebEV9lV8d8y8imTbtsHFw5oHz2FSiYpI5k utuJP3PEaFS83X5mLq/ALTsnAxxHrHa4yvLh7YwMyVfRXOPEiutVSTnuqKuduRZlTWbI 3m/KBH+2UtRjPfUEnismV6ozdInfnRHsKNdp9YGwkvR03LCtOht3mZzPsdAhn2EQB5uQ KDTJFDQ2IUMHD1EvELPC4y8f/Fpa7pCGIcHa7CU+Hj62MKWS2sJZIXSRErCr/q74xvHz us9w== X-Gm-Message-State: AOAM533cIneUB+dLZURdb0eIbhq7ENzbDDki5LNyVaFvXvYElKFE9QHe AQgVe0H7H2ZJesa3ah4F6S0= X-Google-Smtp-Source: ABdhPJzap437musxU3jzCq6oCSQENi5Ye3w5VETr/JyJb4UHmrFusSZ0ZYaQyc9frWM8uLRPVHetRA== X-Received: by 2002:a17:90a:520e:: with SMTP id v14mr25761223pjh.9.1609681029640; Sun, 03 Jan 2021 05:37:09 -0800 (PST) Received: from localhost (180-150-91-8.b4965b.per.nbn.aussiebb.net. [180.150.91.8]) by smtp.gmail.com with ESMTPSA id k18sm17774738pjz.26.2021.01.03.05.37.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 03 Jan 2021 05:37:09 -0800 (PST) References: <87pn38s5wo.fsf@posteo.net> <87ft3itiu2.fsf@gmail.com> <87sg7ijhi5.fsf@posteo.net> User-agent: mu4e 1.4.13; emacs 27.1 From: TEC To: Juan Manuel =?utf-8?Q?Mac=C3=ADas?= Subject: Re: [PATCH] A proposal to add LaTeX attributes to verse blocks Date: Sun, 03 Jan 2021 21:08:30 +0800 In-reply-to: <87sg7ijhi5.fsf@posteo.net> Message-ID: <87eej2ta4e.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::632; envelope-from=tecosaur@gmail.com; helo=mail-pl1-x632.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: orgmode Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.03 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=gMrrFhwE; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Migadu-Queue-Id: 434C09403D5 X-Spam-Score: -3.03 X-Migadu-Scanner: scn0.migadu.com X-TUID: KAH1l8iltEwq Juan Manuel Mac=C3=ADas writes: > Thank you very much for your response and your comments. Seriously, thanks for the patch. I think the ML is usually a bit more responsive, but it seems to be a bit quiet at the moment. > I agree to name "Insert, include, etc." the attribute to include > arbitrary LaTeX code, better than "options". Glad my feedback seems to have gone down well :). If the only likely use of this is adjusting the font, perhaps for the sake of consistency we can match the behaviour of tables, which take a :font LaTeX attribute? > Of course, I can add the necessary documentation to the files you tell > me. As I am new to submitting patches, I don't really know how to > proceed: do I have to send you the new version of the patch, with the > documentation? Should I send a new email with all of it to this list? Thanks for asking. Sometimes it seems the maintainers take the trouble of adding an ORG-NEWS entry or minor touching ups to the patch, but I think it's nice to leave as little for them to do as possible :) Announce changes in: etc/ORG-NEWS Document new/different behaviour in: doc/org-manual.org I think Markup for /Rich Contents > Paragraphs/ may be the right place to add a description of this functionality --- verse blocks are discussed around line 10750. Regarding how patches on this ML work, this is what I've observed: - Initial version of patch submitted, with justification/explanation - Feedback may be given - Revisions of the patch are attached in replies to feedback - Process repeats until everyone's happy - Patch is merged i.e. it all tends to happen in the same thread. Hope this helps, Timothy.