emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Akater <nuclearspace@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Do not inherit unnumbered property: help needed
Date: Sun, 19 Nov 2017 00:28:34 +0100	[thread overview]
Message-ID: <878tf3p3od.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <481BE455-C966-461F-85E2-327820D31392@gmail.com> (Akater's message of "Sat, 18 Nov 2017 18:50:31 +0000")

Hello,

Akater <nuclearspace@gmail.com> writes:

> I got an impression that UNNUMBERED's children get cut off prior to
> what user can do,

UNNUMBERED headings are not cut off, at least not by "ox.el".

> hence writing a simple backend won't help, and I'll have to patch org
> (ox) source. Do you know for sure I'm wrong?

I'm quite certain you're wrong.

> That's what I asked for
> originally---which function is responsible for excluding unnumbered's
> children from exported entries.

Three functions actually check UNNUMBERED properties:

- org-export-numbered-headline-p
- org-export-collect-headlines
- org-export-excluded-from-toc-p

You can ignore the last two because it's a special case (when value is
"notoc").

So, if you want to control UNNUMBERED property, just don't trust
`org-export-numbered-headline-p', or any function calling it.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-11-18 23:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 11:56 Do not inherit unnumbered property: help needed Akater
2017-11-17 12:21 ` Kaushal Modi
2017-11-17 14:19   ` Akater
2017-11-17 22:09     ` Nicolas Goaziou
2017-11-18 17:01       ` Akater
2017-11-18 17:18         ` Nicolas Goaziou
2017-11-18 18:35           ` Akater
2017-11-18 18:50           ` Akater
2017-11-18 23:28             ` Nicolas Goaziou [this message]
2017-11-21 22:52               ` Nicolas Goaziou

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=878tf3p3od.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=nuclearspace@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).