From: Ken Mankoff <mankoff@gmail.com>
To: Nicolas Girard <girard.nicolas@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Eric Schulte <schulte.eric@gmail.com>,
Mark Edgington <edgimar@gmail.com>
Subject: Re: proposal to have ignoreheading tags/properties
Date: Thu, 12 Jun 2014 15:26:42 -0400 [thread overview]
Message-ID: <m2vbs5q5mm.fsf@gorgonzola.lan> (raw)
In-Reply-To: <CANMKmefZhHipUtcPm7qtg25_YwZJXXav5MFUnKt4ATy0v+uazg@mail.gmail.com>
On 2014-06-12 at 15:21, Nicolas Girard wrote:
> I also ran across this need. What I had in mind was that certain todo
> types would be treated as inline.
> ...
> Such a feature is more generic and would be useful in other contexts ;
> and the LaTeX-related issues discussed in this thread would be solved
> using something like
> * INLINE appendix
> \appendix
> * Appendix 1
In your example, I cannot collapse "* Appendix 1 "under "INLINE
appendix". I need to add a "*" to it, and it is now at the incorrect
level when exporting. There is no point in having the "INLINE appendix"
here.
I'm not sure how this feature using TODO keywords is "more generic"
(also, more generic than what?). TODO types have a very specific
functionality, and I think one can only have 1 TODO type. So if you
wanted to have
* INLINE TODO foo
or
* WAITING INLINE bar
It would not work.
Implementing this feature as tags allows one to use existing TODO
items. Tags are already a more generic item so adding a new behavior
isn't that dramatic (and is it new? :noexport: already exists), and
multiple tags are supported. It seems a better place for the
implementation.
I vote for the following tags:
+ :noexport: Does not export item, content, and children.
+ :ignoreheading: Does not export heading. Exports content and children.
+ :ignorecontent: Does not export heading or content. Does export children.
+ :ignorebranch: Does not export heading, content, or children.
+ :promotesubheadings: Promotes children headings, regardless of
exporting this heading or not
Note that :ignorebranch: is the same as ":noexport" but is a more
consistent naming scheme. Ignoring and promotion are two separate items
and can be used together or exclusively for maximum number of export
behaviors.
In this case, a modified version of your example might look like this:
* Appendix :ignoreheading:promotesubheadings:
\appendix
** Appendix 1
** Appendix 2
-k.
next prev parent reply other threads:[~2014-06-12 19:40 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:49 proposal to have ignoreheading tags/properties Mark Edgington
2014-06-12 17:32 ` Thorsten Jolitz
2014-06-12 17:41 ` Ken Mankoff
2014-06-12 18:11 ` Thorsten Jolitz
2014-06-12 18:16 ` Ken Mankoff
2014-06-13 14:32 ` Rasmus
2014-06-13 15:02 ` Thorsten Jolitz
2014-06-12 18:09 ` Mark Edgington
2014-06-12 18:12 ` Eric Schulte
2014-06-12 18:54 ` Aaron Ecay
2014-06-12 19:21 ` Nicolas Girard
2014-06-12 19:26 ` Ken Mankoff [this message]
2014-06-12 19:52 ` Nicolas Girard
2014-06-13 1:20 ` Samuel Wales
2014-06-12 19:34 ` Nicolas Girard
2014-06-12 20:13 ` Eric Schulte
2014-06-12 22:42 ` Nicolas Girard
2014-06-12 23:36 ` Eric Schulte
2014-06-13 0:35 ` Ken Mankoff
2014-06-13 0:46 ` Eric Schulte
2014-06-13 2:35 ` Ken Mankoff
2014-06-13 11:11 ` Eric Schulte
2014-06-13 3:28 ` Mark Edgington
2014-06-13 14:23 ` Rasmus
2014-06-14 12:43 ` Nicolas Goaziou
2014-06-14 16:48 ` Mark Edgington
2014-06-14 18:12 ` Aaron Ecay
2014-06-14 18:12 ` Nicolas Goaziou
2014-06-14 18:07 ` Aaron Ecay
2014-06-14 18:22 ` Nicolas Goaziou
2014-06-14 22:39 ` Aaron Ecay
2014-06-16 1:14 ` Eric Schulte
2014-06-16 8:08 ` Nicolas Goaziou
2014-06-16 12:19 ` Mark Edgington
2014-06-16 13:29 ` Eric Schulte
2014-06-22 2:03 ` Aaron Ecay
2014-06-22 23:52 ` Eric Schulte
2014-07-27 17:21 ` Bastien
2014-07-28 18:15 ` Mark Edgington
2014-07-28 18:27 ` Rasmus
2014-07-28 19:21 ` Mark Edgington
2014-07-28 19:43 ` Nicolas Goaziou
2014-07-28 22:01 ` Rasmus
2014-07-29 14:31 ` Bastien
2014-08-02 5:16 ` Mark Edgington
2014-08-06 4:09 ` Aaron Ecay
2014-06-13 2:38 ` Eric Abrahamsen
2014-06-13 4:07 ` Mark Edgington
2014-06-13 4:44 ` Eric Abrahamsen
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=m2vbs5q5mm.fsf@gorgonzola.lan \
--to=mankoff@gmail.com \
--cc=edgimar@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=girard.nicolas@gmail.com \
--cc=schulte.eric@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).