From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Ondřej Grover" <ondrej.grover@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH]Extend export hook example for removing headlines with tag ignore_heading
Date: Mon, 13 Apr 2015 21:42:58 +0200 [thread overview]
Message-ID: <87vbgzx1a5.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAOyjJOJNCmEY4=ZT-YZAQGBgUj6QwWPSCAaUx8FzmO++g4bmSA@mail.gmail.com> ("Ondřej Grover"'s message of "Mon, 13 Apr 2015 20:13:38 +0200")
Hello,
Ondřej Grover <ondrej.grover@gmail.com> writes:
Thanks for the patch. Some comments follow.
>> "export" becomes part of the noexport heading.
>>
>> * h0
>> ** h1 :noexport:
>> no export
>> ** h2 :ignore_heading:
>> export
>>
> I have no idea how to get around this. It stems from the basic problem in
> Org mode that there are no entry closures AFAIK: To export the "export" it
> would have to be under a heading that does not have the :noexport:
> tag.
This is why it shouldn't be included in "ox.el". It may be useful, but
it is broken.
It might be fixable with proper specifications and by working at the
parse tree level, tho.
> +Two hooks are run during the first steps of the export process. The
> +first one, @code{org-export-before-processing-hook} is called before
> +expanding macros, Babel code and include keywords in the buffer. The
> +second one, @code{org-export-before-parsing-hook}, as its name suggests,
> +happens just before parsing the buffer. Their main use is for heavy
> +duties, that is duties involving structural modifications of the
> +document. For example, one may want to remove every headline with the
^^^^
missing space
> +@samp{ignore_heading} tag (excluding those with the @samp{noexport} tag)
> +in the buffer and promote their children during export. The following
> code can achieve this:
>
> @lisp
> @group
> -(defun my-headline-removal (backend)
> - "Remove all headlines in the current buffer.
> +(defun ignored-headlines-removal (backend)
> + "Remove all headlines with the ignore_headline tag in the current buffer
> +and promote all child headlines underneath them.
> BACKEND is the export back-end being used, as a symbol."
First sentence in docstrings should fit in a single line.
> (org-map-entries
> - (lambda () (delete-region (point) (progn (forward-line) (point))))))
> + (lambda () (progn (org-map-tree (lambda () (when (> (outline-level) 1)
> + (org-promote))))
> + (delete-region (point) (point-at-eol))))
Nitpick : `point-at-eol' -> `line-end-position'
> + "+ignore_heading-noexport"))
>
> -(add-hook 'org-export-before-parsing-hook 'my-headline-removal)
> +(add-hook 'org-export-before-parsing-hook 'ignored-headlines-removal)
> @end group
> @end lisp
>
> -Note that functions used in these hooks require a mandatory argument,
> -a symbol representing the back-end used.
> +The second argument to the @code{org-map-entries} function is an
> +agenda-style match query string (@pxref{Matching tags and properties}).
> +Note the underscore in the tag, it is not recommended to use the
> +@samp{ignoreheading} tag because the Beamer export backend treates it in
> +a similar, yet more complicated way.
This is really out of the example scope. Also, `org-map-entries' is
already extensively documented in the manual.
> It may also be useful to exclude +the @samp{ignore_heading} tag from
> inheritance (@pxref{Tag +inheritance}).
Also off-topic.
Please keep in mind this is an example to illustrate
`org-export-before-parsing-hook', not really a place to document some
hack.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-04-13 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 15:23 [PATCH]Extend export hook example for removing headlines with tag ignore_heading Ondřej Grover
2015-04-13 16:09 ` Rasmus
2015-04-13 18:13 ` Ondřej Grover
2015-04-13 19:42 ` Nicolas Goaziou [this message]
2015-04-13 22:40 ` Suvayu Ali
2015-04-13 19:59 ` Rasmus
-- strict thread matches above, loose matches on Subject: below --
2015-04-12 11:59 Ondřej Grover
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbgzx1a5.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=ondrej.grover@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).