From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: proposal to have ignoreheading tags/properties Date: Sat, 14 Jun 2014 20:22:04 +0200 Message-ID: <874mznz703.fsf@nicolasgoaziou.fr> References: <87tx7qxahl.fsf@gmail.com> <87ppie2c2h.fsf@gmail.com> <871tutx4t4.fsf@gmail.com> <87mwdfzmox.fsf@nicolasgoaziou.fr> <8761k38ivd.fsf@gmail.com> 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]:37844) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvsaB-0007Ge-4c for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 14:21:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wvsa0-0000TP-VV for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 14:21:39 -0400 Received: from relay4-d.mail.gandi.net ([2001:4b98:c:538::196]:54038) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wvsa0-0000TG-P9 for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 14:21:28 -0400 In-Reply-To: <8761k38ivd.fsf@gmail.com> (Aaron Ecay's message of "Sat, 14 Jun 2014 14:07:50 -0400") 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: Eric Schulte Cc: Nicolas Girard , emacs-orgmode , Mark Edgington Hello, Aaron Ecay writes: > I=E2=80=99m confused. In the text, you say =E2=80=9Cpromoted to the root= 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=9Cpr= omoted > to the level of the highest dominating :noexport: headline=E2=80=9D? Tha= t seems > correct to me (but I have not thought about it extensively). Exactly. I meant "promoted to the root of the :noexport: tree", which is basically what you describe. > 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. I'd rather not introduce more special tags, if possible. I think that this feature should be implemented with :export:/:noexport: before we start pondering about the relevance of some syntactic sugar. There are other ways to handle "same tag on all children", e.g., an interactive function. Regards, --=20 Nicolas Goaziou