From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Org-mode version 5.17
Date: Thu, 20 Dec 2007 22:24:11 +0100 [thread overview]
Message-ID: <87bq8lvz44.fsf@bzg.ath.cx> (raw)
In-Reply-To: <acf852aa0712192228n747ac545wdec3f2381b27337e@mail.gmail.com> (Carsten Dominik's message of "Thu, 20 Dec 2007 07:28:42 +0100")
Hi Carsten,
"Carsten Dominik" <dominik@science.uva.nl> 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-<down>
=> subheadline 1 goes below subheadline 2 [OK]
6. M-<down>
=> 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
next prev parent reply other threads:[~2007-12-20 21:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 6:28 Org-mode version 5.17 Carsten Dominik
2007-12-20 8:36 ` Detlef Steuer
2007-12-20 12:13 ` Carsten Dominik
2007-12-20 13:06 ` Elicket Lee
2007-12-20 13:56 ` Kirill A. Korinskiy
2007-12-20 14:13 ` Carsten Dominik
2007-12-20 14:22 ` Rainer Stengele
2007-12-20 14:30 ` Carsten Dominik
2007-12-20 15:15 ` Rainer Stengele
2007-12-20 21:24 ` Bastien [this message]
2007-12-22 16:49 ` Bastien
2007-12-20 22:36 ` Jose A. Ortega Ruiz
2008-01-15 14:40 ` Carsten Dominik
2007-12-30 11:22 ` Adam Spiers
2008-01-03 9:01 ` Carsten Dominik
2008-01-03 12:48 ` Adam Spiers
2008-05-30 12:21 ` automatically jumping to stored note location Adam Spiers
2008-06-11 5:16 ` Dominik, C.
2008-06-11 10:53 ` Adam Spiers
2008-06-11 17:11 ` Cezar Halmagean
2008-06-11 18:10 ` Manuel Hermenegildo
2008-06-13 8:23 ` Carsten Dominik
2008-06-13 9:38 ` Adam Spiers
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=87bq8lvz44.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--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).