From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Edgington Subject: Re: proposal to have ignoreheading tags/properties Date: Sat, 14 Jun 2014 16:48:58 +0000 (UTC) Message-ID: 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: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53740) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wvr8m-0004IX-N8 for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 12:49:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wvr8f-00026z-El for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 12:49:16 -0400 Received: from plane.gmane.org ([80.91.229.3]:47332) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wvr8f-00026Z-8h for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 12:49:09 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Wvr8d-0003S4-V5 for emacs-orgmode@gnu.org; Sat, 14 Jun 2014 18:49:08 +0200 Received: from c-71-238-75-211.hsd1.mi.comcast.net ([71.238.75.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 14 Jun 2014 18:49:07 +0200 Received: from edgimar by c-71-238-75-211.hsd1.mi.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 14 Jun 2014 18:49:07 +0200 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: emacs-orgmode@gnu.org Nicolas Goaziou nicolasgoaziou.fr> writes: > Actually, the problem is deeper than that. This :inline: tag is just > a convoluted way to ask for a positive answer to another FAQ: « Can > I close an outline section without starting a new section? » > (http://orgmode.org/worg/org-faq.html#closing-outline-sections). Indeed, > allowing :include: tags is equivalent to allowing to close sections > before the next one, at least at the export level: > > * Section one > > Some text > > ** Subsection one > > Some text > > ** Subsection two > > Some text > > ** end Subsection Two :inline: > > Continue text in section one. > If I understand your example correctly, it seems like you are assuming that the :inline: tag should promote a section's contents to the level *above* the level of the section having the :inline: tag. To me this behavior doesn't make sense, and that's also not what I would expect such a tag to do -- instead, the section's text (anything which comes before the next headline at any level) should be merged with the text of the nearest preceding headline. Then all nested headlines contained in the :inline: section should be promoted. It is true that this could sometimes be confusing. For example: * A text1 ** B text2 * C :inline: text3 ** D text 4 would get treated like: * A text1 ** B text2 text3 * D text 4 In this case, one would likely omit 'text3' from the first part of the example, since it doesn't make much sense to have it there. For the most part, though, it would be a behavior that makes sense (e.g. if "* C" were replaced with "** C" in the example). It may be that "inline" isn't the best word to describe this behavior, which is why something with "ignore" or "promotechildren" has been mentioned.