emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Peter Jones <mlists@pmade.com>
To: emacs-orgmode@gnu.org
Subject: Correct Way to Create Sibling Headings
Date: Thu, 11 Sep 2008 15:08:58 -0600	[thread overview]
Message-ID: <86fxo6tmol.fsf@pmade.com> (raw)

I'm aware of two ways to create a sibling heading (a heading directly
after the current heading):

  1. M-return (org-meta-return)
  2. C-return (org-insert-heading-after-current)

They both operate slightly differently, but neither seem to do what I
want.

org-meta-return creates a heading directly after the current heading,
but before the properties and content of the original heading.
org-insert-heading-after-current collapses the current heading before
creating the next heading, keeping properties and content in their
correct location.

I tend to use org-insert-heading-after-current to get around this side
effect of org-meta-return, but org-insert-heading-after-current doesn't
support the same features that org-meta-return does:

 - Using the shift key to make the new heading a TODO item
 - Creating a heading *above* the current heading when used at the BOL

Plus, org-insert-heading-after-current also collapses the open headings
around it, which is often not what I want since it removes context
information.

I guess I have two questions:

  1. Is there a bug in org-meta-return that assigns the properties and
     content of the current heading to the newly created heading?

  2. What is the intended difference between M-return and C-return?

Thanks.

-- 
Peter Jones, http://pmade.com
pmade inc.  Louisville, CO US

next             reply	other threads:[~2008-09-11 21:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 21:08 Peter Jones [this message]
2008-09-13  3:16 ` Correct Way to Create Sibling Headings Daniel Clemente
2008-09-13 19:57 ` Carsten Dominik
2008-09-13 23:17   ` Peter Jones

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=86fxo6tmol.fsf@pmade.com \
    --to=mlists@pmade.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

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).