emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Neil Jerram <neil@ossau.homelinux.net>
To: alain.cochard@unistra.fr, emacs-orgmode@gnu.org
Subject: Re: How to move up/down a headline but not the subtree?
Date: Thu, 05 Jul 2018 11:46:41 +0100	[thread overview]
Message-ID: <87lgaq0xke.fsf@ossau.homelinux.net> (raw)
In-Reply-To: <23357.59250.52090.498378@frac.u-strasbg.fr>

Alain.Cochard@unistra.fr writes:

> Hello.  
>
> I am aware of org-move-subtree-up/down, which moves the entire
> subtree. 
>
> I am also aware of org-shiftmetaup/down which moves the line[fn:1] (also
> works for a headline).
>
> 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.

My view/guess: because the subheadings are an integral part of the
content of the containing item.

Wouldn't you agree?  It seems to me like a fairly fundamental aspect of
the Org model.

That said, perhaps your use case is one where you've realized that
subheadings don't actually belong to the containing item?  In that case,
what could make more sense is to promote (or kill and yank elsewhere)
all of the wrongly placed subheadings.  You could promote an individual
subheading with M-S-left, or kill and yank it with C-c C-x C-w and C-c
C-x C-y, but I don't know if there's an easy way to repeat that over all
subheadings.

Another possible approach: what about demoting just the containing
heading with M-left and then killing/yanking that elsewhere?

Regards,
   Neil

  parent reply	other threads:[~2018-07-05 10:46 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 [this message]
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
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=87lgaq0xke.fsf@ossau.homelinux.net \
    --to=neil@ossau.homelinux.net \
    --cc=alain.cochard@unistra.fr \
    --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).