From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Mankoff Subject: Re: proposal to have ignoreheading tags/properties Date: Thu, 12 Jun 2014 15:26:42 -0400 Message-ID: References: <87tx7qxahl.fsf@gmail.com> <87ppie2c2h.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42935) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvAqu-00086d-NP for emacs-orgmode@gnu.org; Thu, 12 Jun 2014 15:40:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WvAqh-0003wF-Mb for emacs-orgmode@gnu.org; Thu, 12 Jun 2014 15:40:00 -0400 Received: from mail-qa0-x233.google.com ([2607:f8b0:400d:c00::233]:40155) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WvAqh-0003wB-It for emacs-orgmode@gnu.org; Thu, 12 Jun 2014 15:39:47 -0400 Received: by mail-qa0-f51.google.com with SMTP id j7so1072257qaq.10 for ; Thu, 12 Jun 2014 12:39:47 -0700 (PDT) In-reply-to: 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 Girard Cc: emacs-orgmode , Eric Schulte , Mark Edgington 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.