From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mark Edgington <edgimar@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: proposal to have ignoreheading tags/properties
Date: Sat, 14 Jun 2014 20:12:54 +0200 [thread overview]
Message-ID: <878uozz7fd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <loom.20140614T182700-729@post.gmane.org> (Mark Edgington's message of "Sat, 14 Jun 2014 16:48:58 +0000 (UTC)")
Hello,
Mark Edgington <edgimar@gmail.com> writes:
> 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.
I'm always assuming the worst.
> 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).
As I said, you cannot solve that confusing situation in the general
case. If we allow the confusing part (i.e "text3") altogether, then my
suggestion still holds:
- if you don't need to nest headlines, use a drawer.
- if you do need sub-headings, extending :export: and :noexport: is
sufficient.
Example:
* A
text1
** B
text2
* C :noexport:
text3
** D :export:
text
If you really need the exact behaviour that you describe, I suggest to
extend the first answer to the relative FAQ so that it also promotes
sub-headings besides removing the headline.
> 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.
The fact that it's difficult to find a good descriptive name for that
feature is a good indication that it isn't meant for general
consumption. ;)
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-06-14 18:12 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
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 [this message]
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=878uozz7fd.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=edgimar@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).