From: Skip Collins <skip.collins@gmail.com>
To: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: How to signal end of a section or subsection
Date: Mon, 20 Jan 2014 11:30:58 -0500 [thread overview]
Message-ID: <CABUh-74ThQ-_QH0TRNbKJDW4sk=N74YdUfxCeqwHiKGts15deg@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.00.1401141001360.33044@tbetbambyn.jubv.rqh>
Several requests have been made over the years for a way to end a
subsection without starting a new new higher level section. This is
possible with plain lists: a blank line ends the list. Some other
syntax would have to be added to org to allow this for sections. I
would love to see something like this implemented:
--- begin org example ---
* First top-level section
A bunch of text.
Blah blah.
Yada yada.
** TODO Something I need to do
** :END:
Resuming first top-level section.
** Here is a small subsection
When this sub-section ends, the top-level section will resume.
** :END:
Resuming first top-level section.
--- end org example ---
Such a fundamental change to org syntax might be difficult to
implement without extensive changes to how files are parsed. But,
IMHO, it would add to its elegance and flexibility. As things stand
now, inline tasks and lists are used as workarounds.
next prev parent reply other threads:[~2014-01-20 16:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 15:12 How to signal end of a section or subsection Ken Mankoff
2014-01-14 16:55 ` Eric S Fraga
2014-01-15 12:24 ` Ken Mankoff
2014-01-15 17:15 ` Eric S Fraga
2014-01-20 16:30 ` Skip Collins [this message]
2014-01-21 16:41 ` Eric S Fraga
2014-01-22 20:16 ` Alan Schmitt
2014-01-22 20:22 ` Nicolas Goaziou
2014-01-22 21:38 ` Sebastien Vauban
2014-01-22 22:20 ` Nicolas Goaziou
2014-01-23 8:17 ` Sebastien Vauban
2014-01-23 11:14 ` Nicolas Goaziou
2014-01-23 22:20 ` Sebastien Vauban
2014-01-22 21:45 ` Alan Schmitt
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='CABUh-74ThQ-_QH0TRNbKJDW4sk=N74YdUfxCeqwHiKGts15deg@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).