From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Org-mode version 5.17 Date: Thu, 20 Dec 2007 22:24:11 +0100 Message-ID: <87bq8lvz44.fsf@bzg.ath.cx> References: 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 1J5SsN-0000UD-5A for emacs-orgmode@gnu.org; Thu, 20 Dec 2007 16:24:19 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1J5SsK-0000Sx-Cy for emacs-orgmode@gnu.org; Thu, 20 Dec 2007 16:24:18 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1J5SsK-0000Sq-3N for emacs-orgmode@gnu.org; Thu, 20 Dec 2007 16:24:16 -0500 Received: from nf-out-0910.google.com ([64.233.182.184]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1J5SsJ-0001Gs-NZ for emacs-orgmode@gnu.org; Thu, 20 Dec 2007 16:24:15 -0500 Received: by nf-out-0910.google.com with SMTP id f5so17223nfh.26 for ; Thu, 20 Dec 2007 13:24:14 -0800 (PST) In-Reply-To: (Carsten Dominik's message of "Thu, 20 Dec 2007 07:28:42 +0100") 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 Hi Carsten, "Carsten Dominik" writes: > I am releasing version 5.17 of org-mode, hopefully the last release > before the holidays. Lots of stuff is still on my TODO list, but this > is how far I have gotten. That's great! Thanks a lot. > - When cutting, pasting, or moving subtrees and items, the > empty lines *before* the subtree/item now belong to the > part and will be moved with it. There is one exception to > this rule: If the first child is moved down (or, > equivalently, the second is moved up), the amount of empty > lines *above* the first child to be moved along with it is > limited by the number of empty lines *below* it. This > sounds complicated, but it allows to have extra empty space > before the first child and still have good behavior of the > subtree motion commands. Here is the only slight oddity I've found so far: when moving folded trees, sometimes the moved tree will be swallowed in the previous or next fold... Here is an example: --8<---------------cut here---------------start------------->8--- #+TITLE: Test file #+STARTUP: fold * headline 1 ** subheadline 1 Content. ** subheadline 2 Content. ** subheadline 3 Content. --8<---------------cut here---------------end--------------->8--- 1. make sure this file is folded 2. go to headline 1 3. TAB to unfold 4. go to subheadline 2 5. M- => subheadline 1 goes below subheadline 2 [OK] 6. M- => subheadline 1 disappears (is in subheadline 3 fold) IIRC, moving subtrees never ended up in them disappearing before. Is there a simple way to make sure that the moving subtree always remains visible? Thanks! And happy holidays -- -- Bastien