Ken Mankoff <mank...@gmail.com> writes: > Hi Eric, On 2014-06-12 at 20:46, Eric Schulte wrote: >> Can you suggest a more intuitive/appropriate tag name? I'm not >> personally partial to "inline", it was just the first thing that >> occurred to me. Previous implementations of similar behavior used >> the tag "prelim". > > I posted the following before. I think you might not be getting all > the emails I post to the list. For example, I commented that INLINE as > a TODO keyword didn't make sense to me using a similar explanation to > your reply to that same email. I have used your implementation from > last week using "prelim" but changed the word, because as with > "inline", I don't associate the word "prelim" with the behavior being > implemented. >
Sounds like I'm missing something. > > -k. > > 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. This feels excessive to me. "ignorecontent" could more easily be implemented with a leading ignored heading, and the common use case of promoting a heading's children while ignoring the heading itself now requires two tags with long names. Best, Eric -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D (see https://u.fsf.org/yw)
