From: Skip Collins <skip.collins@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Continuation of main section text after subsections
Date: Mon, 25 Apr 2011 20:02:37 -0400 [thread overview]
Message-ID: <BANLkTinprR7S9uq4bU2hVyXY2jCKdFJc6g@mail.gmail.com> (raw)
Marcel van der Boom <marcel <at> hsdev.com> writes:
> My personal conclusion was, given proper outlining and no or very few
> assumptions about indentation preferences, it would be very difficult or
> confusing to implement.
>
> The amount of alternatives given in the thread gave me enough food for
> a while to try out if those would be sufficient. So far, the inline
> tasks (see below) seem to fit my need the best, although their use
> feels a bit like a hack to me.
It seems like a hack to me as well. I would very much like to see this
feature implemented but am not very happy with the inline task
workaround. The reason inline tasks work for this purpose is that they
allow for a termination string. This is also true for plain lists
which terminate with two blank lines by default. It would be useful
and logical to allow for a section terminator as well. This could be
done very simply with a '/' character after (or before?) the
appropriate number of asterisks, similar to the way html tags are
terminated:
* Here is a top-level heading
This text follows the top level heading.
** This is a sub-section heading
Here is some text within the sub-section.
*** The sub-section contains an even lower level
This text is part of the sub-sub-section.
**/
Now we resume the top-level section. The string "**/" terminates both
the 2nd and 3rd level sections. If a section terminates in this way,
the next highest level continues where it left off. Section
terminators would be strictly optional, sort of like </p> in html.
Would this be a sensible, feasible thing to implement? I understand
that it may cause difficulty for some exporters. But I don't think
that org features should be limited by what other formats can easily
handle, especially since there are some obvious workarounds for latex
and html.
next reply other threads:[~2011-04-26 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 0:02 Skip Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-28 1:07 Continuation of main section text after subsections Samuel Wales
2011-03-28 4:18 ` Thomas S. Dye
2011-03-28 7:09 ` Sébastien Vauban
2011-04-18 15:34 ` Colin Fraizer
2011-04-18 16:17 ` Marcel van der Boom
2011-04-18 16:42 ` Colin Fraizer
2011-04-18 18:32 ` Jeff Horn
2011-03-28 14:42 ` Nick Dokos
2011-03-28 14:50 ` Marcel van der Boom
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=BANLkTinprR7S9uq4bU2hVyXY2jCKdFJc6g@mail.gmail.com \
--to=skip.collins@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).