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

From: Bernt Hansen <bernt@norang.ca>
To: alain.cochard@unistra.fr
Cc: Neil Jerram <neil@ossau.homelinux.net>, emacs-orgmode@gnu.org
Subject: Re: How to move up/down a headline but not the subtree?
Date: Tue, 10 Jul 2018 13:51:25 -0400	[thread overview]
Message-ID: <87o9ffm12a.fsf@norang.ca> (raw)
In-Reply-To: <23358.220.12819.903256@frac.u-strasbg.fr> (Alain Cochard's message of "Thu, 5 Jul 2018 13:28:28 +0200")

Alain.Cochard@unistra.fr writes:

> Neil Jerram writes on Thu  5 Jul 2018 11:46:
>
>  > > What I would like to do is to be able to move a headline with
>  > > everything up to (but not including) its first subheading.
>  > >
>  > > Does anyone know how to do that?  
>  > >
>  > > I am also interested in knowing if there are specific (deep?)
>  > > reasons why this seemingly basic operation, which I see as the
>  > > analogous of org-do-promote/demote and perform very often with
>  > > standard (but tedious) emacs editing commands, is not already
>  > > implemented.

This only works if the task you want to deal with is level 2 or greater
(i.e. there is a level 1 task above it)

M-S-left M-right C-c C-w (use refile to move this heading somewhere
else)

This promotes all the subheadings one level and detaches the head from
the following stuff so you can move it alone.

Is that what you are looking for?

I regularly capture single level tasks and refile things into trees
later.  If it's filed wrong changing the structure isn't all that hard
with the above commands.  You just don't want to leave the subtasks
orphaned without a parent task (by skipping a level) so that is why I
promote with sublevels first and then demote just the parent task so it
becomes the same level as the subtasks.

Hope that helps.

Regards,
Bernt

next prev parent reply	other threads:[~2018-07-10 17:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-05  9:40 How to move up/down a headline but not the subtree? Alain.Cochard
2018-07-05  9:44 ` Eric S Fraga
2018-07-05 10:38   ` Alain.Cochard
2018-07-05 10:46     ` Eric S Fraga
2018-07-05 12:07       ` Alain.Cochard
2018-07-05 13:39         ` Eric S Fraga
2018-07-05 10:46 ` Neil Jerram
2018-07-05 11:28   ` Alain.Cochard
2018-07-05 12:53     ` Neil Jerram
2018-07-06 12:45       ` Alain.Cochard
2018-07-10 17:51     ` Bernt Hansen [this message]
2018-07-05 10:50 ` Nicolas Goaziou
2018-07-06 11:59   ` Alain.Cochard
2018-07-07  8:20     ` Nicolas Goaziou

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=87o9ffm12a.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=alain.cochard@unistra.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=neil@ossau.homelinux.net \
    /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).