From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Jones Subject: Correct Way to Create Sibling Headings Date: Thu, 11 Sep 2008 15:08:58 -0600 Message-ID: <86fxo6tmol.fsf@pmade.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KdtVQ-00077t-FU for emacs-orgmode@gnu.org; Thu, 11 Sep 2008 17:15:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KdtVM-00074w-Mb for emacs-orgmode@gnu.org; Thu, 11 Sep 2008 17:15:09 -0400 Received: from [199.232.76.173] (port=44771 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KdtVL-00074T-W5 for emacs-orgmode@gnu.org; Thu, 11 Sep 2008 17:15:08 -0400 Received: from main.gmane.org ([80.91.229.2]:44056 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KdtVL-0000uR-R9 for emacs-orgmode@gnu.org; Thu, 11 Sep 2008 17:15:08 -0400 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1KdtVH-0000Uf-24 for emacs-orgmode@gnu.org; Thu, 11 Sep 2008 21:15:03 +0000 Received: from 71-218-83-242.hlrn.qwest.net ([71.218.83.242]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Sep 2008 21:15:03 +0000 Received: from mlists by 71-218-83-242.hlrn.qwest.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Sep 2008 21:15:03 +0000 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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