From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alain.Cochard@unistra.fr
Cc: emacs-orgmode@gnu.org
Subject: Re: How to move up/down a headline but not the subtree?
Date: Sat, 07 Jul 2018 10:20:55 +0200 [thread overview]
Message-ID: <8736wv3194.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <23359.22951.446973.150428@frac.u-strasbg.fr> (Alain Cochard's message of "Fri, 6 Jul 2018 13:59:35 +0200")
Hello,
Alain.Cochard@unistra.fr writes:
> I do not understand this. When one is demoting/promoting
> headlines[fn:2] (and even whole subtrees), it seems to me that one is
> implicitly admitting that the structure is wrong. I only see a
> quantitative difference (i.e., not a qualitative one) between doing
> this and performing want I want to do.
This is indeed a quantitative difference. demoting/promoting is quite
natural, predictable, and easy to implement. Barring indentation, it
only affects the current line. This is a useful low-level function.
Your suggestion is, OTOH, very vague. You want to move a headline and
its section. Where? What should happen then to the rest of the sub-tree?
Even if properly defined, it would potentially affect a lot of the
document, possibly in a convoluted way.
You certainly have good use for this, but I insist on this point: this
is not a "basic" operation, at all. AFAIU, I do think that such
a complex low-level operation should not be a standard command.
> Only now do I realize that it is probably the same logic which is
> behind the triggering of the error "Cannot move past superior level or
> buffer limit" which occurs when trying to move a subtree. Well, I
> certainly don't appreciate these limitations :-) At least in that case
> I can not too painfully break the law by promoting+moving+demoting...
I cannot answer as I don't know what exactly you want to achieve.
> I understand patches are welcome, but I don't know how to do that yet.
> In that case, is it better that I remain silent?
Not at all. You can see how to contribute there:
<https://orgmode.org/worg/org-contribute.html#patches>.
If you don't have time for the gory details, you can also suggest
a change in the Org manual without formatting it as a patch. Since the
manual is an Org file[1], you don't even have to learn Texinfo.
Regards,
Footnotes:
[1] https://code.orgmode.org/bzg/org-mode/raw/master/doc/org-manual.org
--
Nicolas Goaziou 0x80A93738
prev parent reply other threads:[~2018-07-07 8:21 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
2018-07-05 10:50 ` Nicolas Goaziou
2018-07-06 11:59 ` Alain.Cochard
2018-07-07 8:20 ` Nicolas Goaziou [this message]
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=8736wv3194.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--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).