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 14:07:50 -0400 Message-ID: <8761k38ivd.fsf@gmail.com> References: <87tx7qxahl.fsf@gmail.com> <87ppie2c2h.fsf@gmail.com> <871tutx4t4.fsf@gmail.com> <87mwdfzmox.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]:35751) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvsN0-0003jK-NU for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 14:08:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WvsMr-0003Z4-2e for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 14:08:02 -0400 Received: from mail-qc0-x235.google.com ([2607:f8b0:400d:c01::235]:47993) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvsMq-0003YJ-UT for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 14:07:53 -0400 Received: by mail-qc0-f181.google.com with SMTP id x13so5833247qcv.12 for ; Sat, 14 Jun 2014 11:07:52 -0700 (PDT) In-Reply-To: <87mwdfzmox.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: Nicolas Girard , emacs-orgmode , Mark Edgington Hi Nicolas, Thanks for your thoughts. 2014ko ekainak 14an, Nicolas Goaziou-ek idatzi zuen: > OTOH, the situation could be improved wrt :export: and :noexport: tags. > We could allow nesting :export: tags within :noexport: tags with the > following rule: the :export: headline with the lowest level within > the :noexport: tree gets promoted to the root of the tree. > Other :export: headlines have their level set relatively to this one. > Thus: >=20 > Text before first headline > * H1 > Body1 > ** H2 :noexport: > Body2 > *** H3 > Body3 > *** H4 :export: > Body4 > **** H5 > Body5 >=20 > will be seen as >=20 > Text before first headline > * H1 > Body1 > ** H4 > Body4 > *** H5 > Body5 I=E2=80=99m confused. In the text, you say =E2=80=9Cpromoted to the root l= evel of the tree=E2=80=9D, which I expect to mean promotion to a top-level headline. I= n the example, though, H4 is promoted to second-level. Do you mean =E2=80=9Cprom= oted to the level of the highest dominating :noexport: headline=E2=80=9D? That = seems correct to me (but I have not thought about it extensively). Regardless, I like it very much. >=20 > This is not inlining, since "Body2" is lost anyway, and it may require > to tag all children of a given headline, but it's already better than > the current situation, is robust enough for inclusion in core, and > doesn't require introducing a plethora of new special tags. 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 agree with Mark and others that =E2=80=9Cignore=E2=80=9D (or some variant= like =E2=80=9Cexportignore=E2=80=9D or =E2=80=9Cignoreheading=E2=80=9D) are bett= er names for this tag than =E2=80=9Cinline=E2=80=9D. My vote, FWIW, is that the level of sustained us= er interest justifies the inclusion of this new tag. But I hope it will not be too burdensome, since it just serves as a sort of syntactic sugar and doesn=E2=80=99t require any substantial new semantics (beyond your proposal= for the extension of (no)export). To borrow your example, this would look like: Text before first headline * H1 Body1 ** H2 :ignore: Body2 *** H3 Body3 *** H4 Body4 **** H5 Body5 exports to: Text before first headline * H1 Body1 ** H3 Body3 ** H4 Body4 *** H5 Body5 (Note lack of =E2=80=9CText2=E2=80=9D) --=20 Aaron Ecay