From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: proposal to have ignoreheading tags/properties Date: Sat, 14 Jun 2014 18:39:05 -0400 Message-ID: <87wqcj6rqu.fsf@gmail.com> References: <87tx7qxahl.fsf@gmail.com> <87ppie2c2h.fsf@gmail.com> <871tutx4t4.fsf@gmail.com> <87mwdfzmox.fsf@nicolasgoaziou.fr> <8761k38ivd.fsf@gmail.com> <874mznz703.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39859) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvwbS-0007FN-Ac for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 18:39:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WvwbR-00080I-EU for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 18:39:14 -0400 Received: from mail-qa0-x236.google.com ([2607:f8b0:400d:c00::236]:49724) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvwbR-00080D-AL for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 18:39:13 -0400 Received: by mail-qa0-f54.google.com with SMTP id v10so5408392qac.41 for ; Sat, 14 Jun 2014 15:39:12 -0700 (PDT) In-Reply-To: <874mznz703.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nicolas Goaziou , Eric Schulte Cc: Mark Edgington , emacs-orgmode , Nicolas Girard Hi Nicolas, 2014ko ekainak 14an, Nicolas Goaziou-ek idatzi zuen: >=20 > Hello, >=20 > Aaron Ecay writes: >=20 >> I=E2=80=99m confused. In the text, you say =E2=80=9Cpromoted to the roo= t level of the >> tree=E2=80=9D, which I expect to mean promotion to a top-level headline.= In the >> example, though, H4 is promoted to second-level. Do you mean =E2=80=9Cp= romoted >> to the level of the highest dominating :noexport: headline=E2=80=9D? Th= at seems >> correct to me (but I have not thought about it extensively). >=20 > Exactly. I meant "promoted to the root of the :noexport: tree", which is > basically what you describe. >=20 >> I think under your proposal it would be possible to add a single special >> tag which is equivalent (by definition) to tagging a headline noexport >> and all its children export. This could be implemented as a parse tree >> transformation adding the (no)export tags at an early stage in the export >> code. >=20 > I'd rather not introduce more special tags, if possible. >=20 > I think that this feature should be implemented with :export:/:noexport: > before we start pondering about the relevance of some syntactic sugar. I understand your point about gradualism. >=20 > There are other ways to handle "same tag on all children", e.g., an > interactive function. I think a parse tree filter might work better, since then there is no possibility of the tags inadvertently getting out of sync. But either way, it will be easy to implement based on the extension to (no)export functionality you proposed. Thanks, --=20 Aaron Ecay